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-09 12:08 UTC 5d 2h ago |
36 | 36 freeze | 4.3 min | 36 / 36 | #11329–#11364 |
| 2026-09-30 14:24 UTC 14d 0h ago |
26 | 26 freeze | 3 sec | 26 / 26 | #11157–#11182 |
| 2026-09-16 20:02 UTC 27d 19h ago |
49 | 49 freeze | 18 sec | 49 / 49 | #10921–#10969 |
| 2026-09-13 13:15 UTC 31d 1h ago |
27 | 27 freeze | 6 sec | 27 / 27 | #10852–#10878 |
| 2026-09-11 10:46 UTC 33d 4h ago |
30 | 30 freeze | 1.4 min | 30 / 30 | #10780–#10809 |
| 2026-09-08 07:59 UTC 36d 7h ago |
50 | 50 freeze | 4.2 min | 50 / 50 | #10697–#10746 |
| 2026-08-11 19:12 UTC 63d 19h ago |
32 | 32 freeze | 1.6 min | 32 / 32 | #10405–#10436 |
1–7
of 7
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.