How we find nodes. The crawl starts from the peers our own node is already talking to, plus the standard list of seed servers. It then asks each peer for the peers it knows, and walks outward from there. It paces itself: it speeds up when peers answer and slows down when they do not.
We record an address the moment we hear of one, and track separately whether it ever answered. Those are different facts. Hearing about a node is cheap; confirming one is not. Most addresses we are told about never answer, and a peer that already has a connection from us will refuse a second one.
Addresses are hidden on purpose. Running a node is not consent to being listed by address. A public table of every node and where it sits is a targeting list — for censorship, for harassment, or for someone’s abuse desk. Each node gets a fixed nickname and a rough network area instead. The real address never reaches your browser, so it is not in this page’s data either. The totals below are the part worth publishing, and they cost no operator anything.
Tor nodes are missing, and cannot be found. Our crawler can reach .onion peers if
it is given an address. Zcash has no way to discover them: the two node programs, zcashd and
Zebra, both share peer addresses in a format that cannot carry an onion address. Tor nodes exist. They
are invisible to this method, so the Tor line stays at zero.
One dot per node, placed at its city region — never finer. Colour it by whether a node is keeping up with the chain, or by which software it runs. Click a legend entry to toggle it. A node answering on both IPv4 and IPv6 is one dot where we can tell (our own machines); for other operators the protocol carries no node identity, so a dual-stack node may appear twice.
Loading…
| # | Country | Nodes | At tip | Out of sync | Unknown |
|---|
Each bar is every node confirmed reachable at least once that week. Weekly rather than daily, because one day is not one crawl cycle. The crawler takes far longer than 24h to work through its address book, so a daily series would track our own pace rather than the network's.
Loading…
Which implementation each reachable node is running — the aggregate that makes this map worth publishing.
Loading…
| Network | Node | Range | Location | Client | Version | Sync (when indexed) | First Seen | Last Seen |
|---|
Loading…
| Status | What it means | Addresses |
|---|