Proposal #5688

freeze · executed

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

Target TVPijzV1WasNozwEsrGihYEML8d8mWcKSP
Submitted2025-09-22 10:36 UTC
Executed2025-09-22 11:03 UTC
Interval27.4 min
Submit tx 0a091c88a2909a0a4b845eaf03294a3a60f57328daf68014201a11c984771bcd
Execute tx 32f451e3e9fa11a306daebe5c64891dfe47acef52da57066ad0359cf98bc0ffc

Where this interval sits

Longer than 47% 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. 52 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:36 UTC · block 75,959,101
  2. freeze 2025-09-22 11:03 UTC · block 75,959,649
  3. executed 2025-09-22 11:03 UTC · block 75,959,649

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.