Proposal #7519

freeze · executed

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

Target TXXGcxaDHsboGgGcHN2prqQvUTwpFqMTcD
Submitted2026-03-19 20:40 UTC
Executed2026-03-19 21:36 UTC
Interval56.2 min
Submit tx 11ccdaaa3569eb3640124963fa961c98152e38777c8f3c4e9cf12b72b1ffc3be
Execute tx 51dc131893e99bf5113d6f0f8e722d55b228e22ec5ebe202fc622bc2954b3b27

Where this interval sits

Longer than 57% of the 5,961 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-03-19 20:40 UTC · block 81,095,253
  2. freeze 2026-03-19 21:36 UTC · block 81,096,377
  3. executed 2026-03-19 21:36 UTC · block 81,096,377

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.