Proposal #5692

freeze · executed

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

Target TVbzz1rC3xYRDBtYGCpwjAS19dX6BHDAiS
Submitted2025-09-22 10:36 UTC
Executed2025-09-22 11:05 UTC
Interval28.4 min
Submit tx 6217479fc14cddf5c876ef147596f1450349fd8401aab3d6a7e9b456cbcae620
Execute tx 3bc0b698808a77f16274dba62e7f95648ea718dd021be58d617dcebbcf71f9d3

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. 58 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,107
  2. freeze 2025-09-22 11:05 UTC · block 75,959,675
  3. executed 2025-09-22 11:05 UTC · block 75,959,675

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.