Proposal #9776

freeze · executed

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

Target TGnSzxUzingyHJkFQfbKX6DJuaW27fpPWi
Submitted2026-06-29 15:23 UTC
Executed2026-06-29 16:00 UTC
Interval37.4 min
Submit tx dfd34a00e0088cacc08b792d32d2acd3f6501bbbaefec050768922afa23062df
Execute tx 90893f89ad1089f23fec41697c393bcfff31bc777c60c181f2b5f40e40b315d5

Where this interval sits

Longer than 50% 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-06-29 15:23 UTC · block 84,025,632
  2. freeze 2026-06-29 16:00 UTC · block 84,026,379
  3. executed 2026-06-29 16:00 UTC · block 84,026,379

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.