Proposal #5749

freeze · executed

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

Target TK2qsXyDvRiCtgDvxeC6ndkqY1zhPYG8aa
Submitted2025-09-22 10:48 UTC
Executed2025-09-22 11:15 UTC
Interval26.6 min
Submit tx 03bb50e19d00e6777c77a6accca1ec51c1d21b2f9ca706cdea40131341d2bf4f
Execute tx f2fa332beb1eb0cf7d297079586733e4e59ef401141d64fb5c215c7de70baf08

Where this interval sits

Longer than 46% 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. 114 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:48 UTC · block 75,959,346
  2. freeze 2025-09-22 11:15 UTC · block 75,959,879
  3. executed 2025-09-22 11:15 UTC · block 75,959,879

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.