Proposal #10782

freeze · executed

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

Target TZ7LmC6zBipRx6tDMavbzaF8piBpw89cNz
Submitted2026-09-11 10:46 UTC
Executed2026-09-11 11:33 UTC
Interval46.8 min
Submit tx 55ba9dfce3ec09cfee5c6cca80c83f1741b51ccdfd62dce9d3ff0946c899041d
Execute tx 98463d6ac7907828e56d49ece8ea4f34a362b8eeaa9fccaacd39f4c21a49354f

Where this interval sits

Longer than 53% of the 5,899 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.

Part of a batch. 29 other proposals went out within ten minutes either side of this one. Freezes are issued in sweeps, not one at a time — so this address was probably not singled out. See the whole sweep.

What happened on chain

  1. proposal 2026-09-11 10:46 UTC · block 86,150,512
  2. freeze 2026-09-11 11:33 UTC · block 86,151,448
  3. executed 2026-09-11 11:33 UTC · block 86,151,448

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.