Proposal #10756

freeze · executed

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

Target TE7Fecv2PmrHiYAtisis2F29cSEPvJCeBF
Submitted2026-09-09 14:21 UTC
Executed2026-09-09 14:41 UTC
Interval19.9 min
Submit tx f3b38601f9d80b2a84ee3236259bcb349f16bff828a41c68bbd3ce0ad4357fb8
Execute tx fa05d57dae6bdd71cc18ffb92691d25127147a4ba5d1e431419c572f59292a63

Where this interval sits

Longer than 42% 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-09-09 14:21 UTC · block 86,097,242
  2. freeze 2026-09-09 14:41 UTC · block 86,097,641
  3. executed 2026-09-09 14:41 UTC · block 86,097,641

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.