Proposal #7337

unfreeze · executed

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

Target TVWrp9mrjR63uyNh9e3KJPLBSKvHaZdCW4
Submitted2026-03-06 15:49 UTC
Executed2026-03-06 16:22 UTC
Interval32.2 min
Submit tx 865ba41b4a449d31f5d42eb86c82968400b8ef99f3ab39bcf8455a414a0b8737
Execute tx 46f8db79a8c7ede97e6f7043ab4e9ea26f214bab0890e1f847d5aa42e802dd05

Where this interval sits

Longer than 49% of the 5,922 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-06 15:49 UTC · block 80,715,160
  2. unfreeze 2026-03-06 16:22 UTC · block 80,715,804
  3. executed 2026-03-06 16:22 UTC · block 80,715,804

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.