Proposal #5596

unfreeze · executed

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

Target TY8WN8GLdqQA3VeNWDVSkciuLvPH2hEiRW
Submitted2025-09-09 14:53 UTC
Executed2025-09-09 15:45 UTC
Interval51.5 min
Submit tx 1ca0d86a2b532dc4a8d24379f40af877445447962a4475831e38f25c8f394aa9
Execute tx 8fba0fc61f90ffb9181f2dd82d1ee0c6d44c00692a3d42aebd7ca8eb7c52bde6

Where this interval sits

Longer than 55% 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. 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:53 UTC · block 75,589,971
  2. unfreeze 2025-09-09 15:45 UTC · block 75,591,002
  3. executed 2025-09-09 15:45 UTC · block 75,591,002

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.