Proposal #5605

freeze · executed

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

Target TVb58inroehH6xnnd7ByryxejR67uh9xWw
Submitted2025-09-09 14:58 UTC
Executed2025-09-09 15:45 UTC
Interval46.9 min
Submit tx a298da1afa1e93c4103c82e5cff59b2319ebca3dc076a086e6005ea04aa49f70
Execute tx 3432a03a084a60d349dd708b0aaded6a70a64d8e7aa4b01feee196c807187584

Where this interval sits

Longer than 54% 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. 28 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-09 14:58 UTC · block 75,590,077
  2. freeze 2025-09-09 15:45 UTC · block 75,591,014
  3. executed 2025-09-09 15:45 UTC · block 75,591,014

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.