Proposal #11185

freeze · executed

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

Target THwbVuBBb26abe5TrAsYUpYz9mhWnBppdz
Submitted2026-09-30 15:24 UTC
Executed2026-09-30 16:14 UTC
Interval49.5 min
Submit tx 99932e9420aac76bad03f50487a4de2582a30140311588fa5ba19721de0957bc
Execute tx 1f1d5de016f6a9dfc166b05017c6f39f93d6a486b27201415047ac3d3412e9de

Where this interval sits

Longer than 55% of the 5,894 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. 6 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 2026-09-30 15:24 UTC · block 86,703,105
  2. freeze 2026-09-30 16:14 UTC · block 86,704,096
  3. executed 2026-09-30 16:14 UTC · block 86,704,096

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.