Proposal #5718

freeze · executed

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

Target TYCw1yy4q65WeWX2qvTqg4NcWc8j6DUiyh
Submitted2025-09-22 10:40 UTC
Executed2025-09-22 11:13 UTC
Interval33.7 min
Submit tx 689d1cc5e8eed75e860311a2f65f2a1d68a603545ee98ff340c2b988fa629179
Execute tx bed9d67ba798653145aeb7f92fa297a51c8026455e10d983af2515c82d293f40

Where this interval sits

Longer than 50% 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. 103 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:40 UTC · block 75,959,175
  2. freeze 2025-09-22 11:13 UTC · block 75,959,849
  3. executed 2025-09-22 11:13 UTC · block 75,959,849

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.