Proposal #5729

freeze · executed

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

Target TX3Zc232WtQpXQxZ8UwUFaYo2XS45ropWy
Submitted2025-09-22 10:46 UTC
Executed2025-09-22 11:14 UTC
Interval27.8 min
Submit tx b9cd6c717939a2cb1bff9ce5cea4bb05ccdad4bc42ebe26a88f10e7864c8a433
Execute tx 2be9d4744e3e59065407d1e67c25a654434cb4d69db0860c7865fa7f1572e4f4

Where this interval sits

Longer than 48% 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. 129 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:46 UTC · block 75,959,303
  2. freeze 2025-09-22 11:14 UTC · block 75,959,859
  3. executed 2025-09-22 11:14 UTC · block 75,959,859

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.