Proposal #5614

freeze · executed

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

Target TFHM3awxwt2iHuEbobv72NpwXKzgpCb8XS
Submitted2025-09-10 20:03 UTC
Executed2025-09-10 20:30 UTC
Interval27.6 min
Submit tx 65ac9cc10b454aa0f8f725978a1b08efba811fd690a79afed61d366600c67bb4
Execute tx 70b08e5f50a8cdd9b3c22dac363befff4bebb63921647082f4cace9d73556cbf

Where this interval sits

Longer than 47% of the 5,967 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. 8 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-10 20:03 UTC · block 75,624,953
  2. freeze 2025-09-10 20:30 UTC · block 75,625,505
  3. executed 2025-09-10 20:30 UTC · block 75,625,505

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.