Proposal #5585

freeze · executed

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

Target TLQa7efkXqdLTvYEZzfKZSCxM6xpWJxTa3
Submitted2025-09-09 14:50 UTC
Executed2025-09-09 15:44 UTC
Interval53.8 min
Submit tx abc780943a5997e7cec2be91a0aabfd6d875bb76b3e79365f91d4eebfa84fe86
Execute tx 8804737c9e1c89048695a13395d2194fde400b71ac3cb81d2876effe7d85d6d0

Where this interval sits

Longer than 57% 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. 28 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-09 14:50 UTC · block 75,589,918
  2. freeze 2025-09-09 15:44 UTC · block 75,590,994
  3. executed 2025-09-09 15:44 UTC · block 75,590,994

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.