Proposal #5809

freeze · executed

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

Target TVPzR1AgA3KhUjqFxx85z9hk8SwnXvF3KE
Submitted2025-09-22 10:51 UTC
Executed2025-09-22 11:18 UTC
Interval26.4 min
Submit tx eb0b95515ee029da6aebb3ce6f846b3106dc008381e1449d051d1a6153c17e23
Execute tx 83a0338d65d9c8cc6e25c38a675f4e07737d62d1010da4f696d2d012fc1b7e81

Where this interval sits

Longer than 45% 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. 100 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:51 UTC · block 75,959,405
  2. freeze 2025-09-22 11:18 UTC · block 75,959,933
  3. executed 2025-09-22 11:18 UTC · block 75,959,933

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.