don’t trust the JSON
Rebuild it yourself.
Every other page here asks you to believe a file this site generated. This one does not. Pick a sample of the published cohort and your browser re-traces it against the chain from scratch — the same two calls per wallet, the same attribution rule, the same archival confirmation — and then diffs its own answer against what was published. Any disagreement is shown, not smoothed.
Why this is a worker pool and not a loop
The honest version of “we made it fast”
Re-tracing a wallet is two network calls and one JSON.parse. The calls want
concurrency; the parse wants a thread that is not the one painting the page. A signature page
can be tens of megabytes of JSON, and parsing that on the main thread freezes the tab
outright — so the workers parse and discard, handing back a few hundred bytes each.
Whether that is worth anything is a question with a measurable answer, and “Measure the workers” answers it on your machine rather than quoting a number from somebody else’s. The archival confirmation is deliberately left on the main thread and run one at a time: it goes through a proxy to a rate-limited public archive, and fanning it out across eight workers would be rude rather than fast.