WalletExplorer
awaiting buildAleš Janda's manually curated wallet attributions, scraped per-wallet from walletexplorer.com.
Rows in labels.db
0
Confidence
0.85
Refresh cadence
Monthly
Schema
per-subkey
About this source
WalletExplorer.com is a Bitcoin block explorer that has clustered addresses into wallets and labeled the largest ones since 2013. Maintained primarily by Aleš Janda, it covers exchanges, mining pools, gambling sites, payment processors, and historic services long since defunct. We pull the per-wallet CSV export of every labeled wallet on the index page (383 wallets across 5 categories: Exchanges, Pools, Services, Gambling, Old / historic), parse the address columns, and ingest each row tagged with its parent wallet identifier. Each address points back at its wallet page on walletexplorer.com via the source_ref column.
How we got the data
Scraped via tools/scrape_walletexplorer.py with a 3-second crawl delay, generic research User-Agent, and per-wallet CSV export endpoint (?format=csv&page=all). 383 wallet CSVs total, ~1.7 GB raw, ~19 minutes for a full re-fetch.
Why this confidence
High but not perfect. Wallet clustering can mis-merge entities that share a coinjoin or change-address fingerprint, and a few labels are stale (services that rebranded years ago). High enough to be load-bearing in our /address aggregator, low enough that we still defer to direct-disclosure sources (PoR, OFAC) when they agree with a different label.
License & attribution
Public block explorer data. We attribute every row back to its WalletExplorer wallet page so the underlying clustering work is visible to anyone reading our aggregator.
Sample addresses
python tools/build_labels_db.py --update --only walletexplorer
to populate it.
See the data live
Every row from this source is queryable through the /address aggregator and the JSON API.
JSON API Cross-sourceWant this as a feed?
Same data drives the Address Monitoring API: real-time inflow / outflow events on these addresses as they confirm.
About the API