Proposal #10518

freeze · executed

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

Target THoZQpWDLVjFWTuJczGdrDLSKtGQCM8GDb
Submitted2026-08-21 13:40 UTC
Executed2026-08-21 14:39 UTC
Interval58.7 min
Submit tx a9ed7ab31c0b445229a49aa3552da3b007ce9cc06a8c960eaea0a64c56d59995
Execute tx 7c6af5be5cbbb240c3b9e360db9974dbb262eea977e5dcdc029805cb1c6e815d

Where this interval sits

Longer than 58% 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.

Issued alone. No other proposal within ten minutes either side.

What happened on chain

  1. proposal 2026-08-21 13:40 UTC · block 85,549,453
  2. freeze 2026-08-21 14:39 UTC · block 85,550,627
  3. executed 2026-08-21 14:39 UTC · block 85,550,627

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.