Proposal #7871

freeze · executed

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

Target TLxKyEgCVkzdw3cLJHwSvNHbhQAuzxfWcR
Submitted2026-03-27 15:24 UTC
Executed2026-03-27 15:45 UTC
Interval20.9 min
Submit tx 704645ecda9eec32898f8579fe3ddffa2cfbbf16fadc36b2f8998cdde8dcaecf
Execute tx e7a7a12604c990f9880fef7f5415d79e0aa828e5b0a03ed4fdf9b7520ef6ae07

Where this interval sits

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

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

What happened on chain

  1. proposal 2026-03-27 15:24 UTC · block 81,319,276
  2. freeze 2026-03-27 15:45 UTC · block 81,319,693
  3. executed 2026-03-27 15:45 UTC · block 81,319,693

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.