Proposal #5580

freeze · executed

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

Target TP7cTT99L53AFT83UFt752wKM8MWrRdByJ
Submitted2025-09-09 14:50 UTC
Executed2025-09-09 15:44 UTC
Interval53.8 min
Submit tx 00de6d7f1d524c70f14a9e0d8b18182ecf78929fead9e6bcb429e83081b1fcf6
Execute tx d6259397139ba79f1309675ce22912272df7d3d3b5eb6e6387dc49f15cc9b1df

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,914
  2. freeze 2025-09-09 15:44 UTC · block 75,590,990
  3. executed 2025-09-09 15:44 UTC · block 75,590,990

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.