Freezes arrive in sweeps, not one at a time
Every other tracker shows you a list sorted by time, which hides the thing that matters most: whether an address was picked out on its own, or swept up with forty others. Proposals submitted within ten minutes of each other are grouped here as one batch.
| Started (UTC) | Size | Composition | Span | Executed | Proposals |
|---|---|---|---|---|---|
| 2026-10-14 15:25 UTC 2h 20m ago |
15 | 15 freeze | 6 sec | 15 / 15 | #11412–#11426 |
| 2026-10-09 14:06 UTC 5d 3h ago |
11 | 1 freeze · 10 destroy | 3.7 min | 11 / 11 | #11365–#11375 |
| 2026-10-09 12:08 UTC 5d 5h ago |
36 | 36 freeze | 4.3 min | 36 / 36 | #11329–#11364 |
| 2026-10-08 14:05 UTC 6d 3h ago |
10 | 10 freeze | 0 sec | 10 / 10 | #11305–#11314 |
| 2026-10-08 01:10 UTC 6d 16h ago |
17 | 17 freeze | 3.8 min | 17 / 17 | #11288–#11304 |
1–5
of 5
Newer
1 / 1
Older
Where the ten minutes comes from. It is a grouping choice, not a
fact on chain — nothing in the multisig marks where one sweep ends and the next
begins. Ten minutes separates the clusters cleanly in our ledger, and every batch
here lists its own span so you can judge the cut yourself.