Proposal #5685

freeze · executed

The multisig announced this 27.5 min before it took effect. That interval is the only warning anyone got.

Target TWi66CCTwfCcMbKB284pWyjUFj76rFRwbn
Submitted2025-09-22 10:36 UTC
Executed2025-09-22 11:03 UTC
Interval27.5 min
Submit tx 55d934c84accb616f3d06adf9db770daca9f99544f43f4b92919ffd81d4bc503
Execute tx d6b09d5aa8fae94ff2c055bf7eb4ed753fa0320661500e71e00eaafa1f680b93

Where this interval sits

Longer than 47% of the 5,914 executed freezes we hold.

Measured against executed proposals only. Counting the abandoned ones would push every percentile toward 100% and make a long wait read as “about to happen”, which is backwards.

Part of a batch. 52 other proposals went out within ten minutes either side of this one. Freezes are issued in sweeps, not one at a time — so this address was probably not singled out. See the whole sweep.

What happened on chain

  1. proposal 2025-09-22 10:36 UTC · block 75,959,096
  2. freeze 2025-09-22 11:03 UTC · block 75,959,646
  3. executed 2025-09-22 11:03 UTC · block 75,959,646

State events are matched to this proposal by target address and proximity in time. The chain carries no field binding the two, so this pairing is inference — stated plainly rather than presented as proof.

Watch this address

This page is one proposal. The bot tells you the next one, on this address, the second it is submitted.

Watch in Telegram

↑↓ move ↵ open ↵ look it up esc close Nothing you type here is stored or sent anywhere but this lookup.