Proposal #5727

freeze · executed

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

Target TAEKKjTXhKYjewhdsxyk6T8oev8A6PriBu
Submitted2025-09-22 10:45 UTC
Executed2025-09-22 11:14 UTC
Interval28.8 min
Submit tx 9953fc0e3fd18064d6d87122dd60e5ceaa392b702f2b81763663213199e09d9d
Execute tx d81bf50150cc95dbcd94b9a66b824e30a6a6ee905cbbdf47030feee144647ee0

Where this interval sits

Longer than 48% of the 5,966 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. 138 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:45 UTC · block 75,959,282
  2. freeze 2025-09-22 11:14 UTC · block 75,959,857
  3. executed 2025-09-22 11:14 UTC · block 75,959,857

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.