Proposal #6493

freeze · executed

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

Target TDXJuLdVLY3BUVF2FAUSUZeizakZ5yiMHc
Submitted2025-11-22 14:48 UTC
Executed2025-11-22 15:09 UTC
Interval21.4 min
Submit tx 6f02ddec35261f4187acb6cfd7cf1b66462599012f795ccd9bb719d7b21faad8
Execute tx fc314ad9fac1b69839a8a056f9270d43166c3cd73446241292331de5d59b704d

Where this interval sits

Longer than 43% 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 2025-11-22 14:48 UTC · block 77,720,434
  2. freeze 2025-11-22 15:09 UTC · block 77,720,862
  3. executed 2025-11-22 15:09 UTC · block 77,720,862

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.