Proposal #10343

freeze · executed

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

Target TFSG5fu6GoM5K8EvHwWNQXwSsbrRrVPVsa
Submitted2026-08-03 19:58 UTC
Executed2026-08-03 20:17 UTC
Interval18.9 min
Submit tx 53509878a19f947c0b940ea1965fbc052cbceb598d23f920fba19e409939d664
Execute tx eb22b7388d41f7e6a1fed74a7e6d66f59cf15c09f07c98d1203589bea18b238a

Where this interval sits

Longer than 41% 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-08-03 19:58 UTC · block 85,038,765
  2. freeze 2026-08-03 20:17 UTC · block 85,039,143
  3. executed 2026-08-03 20:17 UTC · block 85,039,143

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.