Proposal #5730

freeze · executed

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

Target TPF6cXLiatHpAUBN8p5m8tNQX5dhd4Kh2J
Submitted2025-09-22 10:46 UTC
Executed2025-09-22 11:14 UTC
Interval27.8 min
Submit tx 5591859926a4f8b7a7cb11a408cea1852fc01ffad0f8bd77d6ac681add8dd4e6
Execute tx 8f966fc4b8e0721f070b517a5d6264731038e773534a28172952f69e608280bb

Where this interval sits

Longer than 47% of the 5,966 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. 129 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 2025-09-22 10:46 UTC · block 75,959,304
  2. freeze 2025-09-22 11:14 UTC · block 75,959,860
  3. executed 2025-09-22 11:14 UTC · block 75,959,860

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.