Network Nodes

Publicly reachable Zcash full nodes, discovered by our own continuous P2P crawl -- not a count of every node on the network (many run behind NAT/firewalls and never accept inbound connections, so they're invisible to any crawler), just the ones that answer a handshake. Starts from our own node's current peers plus the standard DNS seeds, then walks outward through each peer's own getaddr gossip. Includes Paces itself adaptively — it speeds up on its own the more peers actually answer and backs off when they don't. Addresses are recorded the moment we hear of one; reachability is tracked separately, because hearing about a node is cheap and confirming one is not (most advertised addresses never answer, and a peer already holding a connection from our address will refuse a second).

Addresses are deliberately masked. Running a node is not consent to being listed by address, and a public table of every node and exactly where it lives is a targeting list — for censorship, for harassment, or for someone’s abuse desk. Each node gets a stable pseudonym plus a coarse network range; the full address is never sent to your browser, so it isn’t in this page’s API response either. The aggregate picture below is the part worth publishing, and it costs no operator anything.

On Tor: the crawler can dial .onion peers through a local SOCKS proxy, but Zcash has no way to discover them — zcashd implements no addrv2 at all, and Zebra only ever sends the legacy addr message, which cannot represent an onion address. Hidden-service nodes exist but are invisible to peer gossip, so the Tor series stays at zero unless an address is supplied out of band.

Where the nodes are

One dot per node, placed at its city region — never finer. Click a legend entry to toggle it. A node answering on both IPv4 and IPv6 is one dot where we can tell (our own fleet); for other operators the protocol carries no node identity, so a dual-stack node may appear twice.

Leaderboard by country

Loading…

#Country Nodes At tip Out of sync Unknown

Visible Nodes (weekly)

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 tracks our own cadence rather than the network's.

Loading…

Node software

Which implementation each reachable node is running — the aggregate that makes this map worth publishing.

Currently visible nodes

Loading…

NetworkNodeRange Location ClientVersionSync (when indexed) First SeenLast Seen

Every address, by status

Loading…

StatusWhat it meansAddresses