Proposal #5734

freeze · executed

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

Target T9yb6vP8o8PQJLNmcCkC9wfk73ULTCy2MB
Submitted2025-09-22 10:46 UTC
Executed2025-09-22 11:14 UTC
Interval27.8 min
Submit tx 87f3135370c031498d92f10ef9b24e93eb71c17c2224c93626b29b519a97d489
Execute tx 84caecac41da1bb63e8697d54a844bce3b6b3e8e47cb306df8456577a1e02085

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. 127 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,307
  2. freeze 2025-09-22 11:14 UTC · block 75,959,863
  3. executed 2025-09-22 11:14 UTC · block 75,959,863

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.