Proposal #5769

freeze · executed

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

Target TJ4WNKttXS4RKkCS8whtGTTETSjLY2v6Nu
Submitted2025-09-22 10:49 UTC
Executed2025-09-22 11:16 UTC
Interval26.5 min
Submit tx 49901161a60f2a0a20a8cb3a622b066ac4bbb4819d0a9b62e5224e410b05c32f
Execute tx fa16e3bddb20ddfadb036b488929a14d6312d0abd1d5e3c2b318e91f2cf13446

Where this interval sits

Longer than 46% 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. 104 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:49 UTC · block 75,959,366
  2. freeze 2025-09-22 11:16 UTC · block 75,959,896
  3. executed 2025-09-22 11:16 UTC · block 75,959,896

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.