Proposal #6021

freeze · executed

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

Target TBwreaSGZy23wkLY7RSe6Edw9HZuCisegB
Submitted2025-10-10 13:12 UTC
Executed2025-10-10 13:31 UTC
Interval18.9 min
Submit tx 4111fa9bce2674291f57b9927636e0d7d0da42ce0960bb74c1df13d8728a5175
Execute tx 9d028e21397891a55d7c2dd919a2ee237e30ae58367d7876a873c9ba05316acc

Where this interval sits

Longer than 41% of the 5,967 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.

Issued alone. No other proposal within ten minutes either side.

What happened on chain

  1. proposal 2025-10-10 13:12 UTC · block 76,480,475
  2. freeze 2025-10-10 13:31 UTC · block 76,480,854
  3. executed 2025-10-10 13:31 UTC · block 76,480,854

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.