Bitcoin Cash

IPFS
Filecoin
Ethereum
Bitcoin
Gnosis
Celestia
Polkadot
Optimism
Base
Litecoin
Bitcoin Cash
Avail
Dogecoin

Overview
Topology
Nodes

Networks
Bitcoin Cash
Nodes

Nodes

Metrics on the state and the connections of reachable Bitcoin Cash nodes, from the version handshake and the address reply of each node. Each address counts as one peer, so a node that listens on IPv4 and on Tor counts two times.

Chain Tip & Sync State

The start height that each node reports in its version message, compared with the most common start height of the crawl (the majority tip). Bitcoin Cash Node and BCH Unlimited do not send the maximum fee filter during the initial block download, so their nodes in the initial block download count as behind or far behind.

Sync State Over Time

Compares the start height that each node reports in its version message with the majority tip, the most common start height of the crawl. A crawl takes up to two hours, so a distance of up to 12 blocks counts as in sync.

In Sync: at most 12 blocks from the majority tip.
Behind and Far Behind: more than 12 and more than 1,008 blocks (one week) below the majority tip.
IBD: initial block download. The node is behind, and it sends the maximum fee filter, which Bitcoin Core does during the initial block download.
Ahead: more than 12 blocks above the majority tip. Such nodes follow another chain.
Height 0: the node reports no blocks.

Online peers per distance to the majority tip

Full screen V

Sync State

Shows the values of the latest crawl.

In Sync: at most 12 blocks from the majority tip.
Behind and Far Behind: more than 12 and more than 1,008 blocks (one week) below the majority tip.
IBD: initial block download. The node is behind, and it sends the maximum fee filter, which Bitcoin Core does during the initial block download.
Ahead: more than 12 blocks above the majority tip. Such nodes follow another chain.
Height 0: the node reports no blocks.

Online peers per distance to the majority tip in the latest crawl

Full screen V

Chain Tips Over Time

Shows the majority tip, the most common start height of the online nodes in a crawl, and the most common start height of the nodes that are more than 12 blocks ahead of it. If there is a "Tip Ahead" line, some nodes follow a chain other than the majority chain. The Sync State chart shows how many nodes and which clients follow it.

Block height of the majority tip and of the tip ahead of it

Full screen V

Suspected Fleets

Online peers that report no blocks, send no addresses, and send an invalid message or no fee filter. These peers are probably no real full nodes. They stay in all other charts.

Suspected Fleets Over Time

Shows the online peers that report start height 0 in their version message, send no address reply, and send an invalid message or no fee filter. Real nodes at the start of the initial block download also report height 0, but they answer the address request. Such peers often run on a few hosting networks with the same user agent and services.

By Fingerprint: the user agent and the services bitmask of the peers.
By ASN: the autonomous system of the peers. Peers without an IP address are in "no ASN".

These peers stay in the counts of all other charts.

Online peers that are probably no real full nodes

Full screen V

Suspected Fleets

Shows the values of the latest crawl.

By Fingerprint: the user agent and the services bitmask of the peers.
By ASN: the autonomous system of the peers. Peers without an IP address are in "no ASN".

These peers stay in the counts of all other charts.

Online peers that are probably no real full nodes in the latest crawl

Full screen V

Address Book & Latency

The addresses that nodes return to a getaddr request, the share of the known addresses that are reachable, and the response times of the nodes per transport.

Address Replies Over Time

Shows the networks of the addresses that the online nodes return to a getaddr request. A reply is a random sample of the node's address book, with up to 1,000 addresses. Select a transport to see, for example, the addresses that Tor nodes return.

Share of the returned addresses per network

Full screen V

Address Replies

Shows the values of the latest crawl.

Share of the returned addresses per network in the latest crawl

Full screen V

Clock Offset Over Time

Shows the absolute difference between the time in the version message of a node and the clock of the crawler. Bitcoin Core warns when the clocks of its peers differ by more than 70 minutes, because a wrong clock can make a node reject valid blocks.

Online peers per clock difference

Full screen V

Clock Offset

Shows the values of the latest crawl.

Online peers per clock difference in the latest crawl

Full screen V

Reachable Addresses Over Time

Shows the share of the addresses per transport that complete the version handshake. The crawler dials all addresses that the nodes return to its getaddr requests. Most of them are stale: the address book of a node also keeps addresses of nodes that went offline long ago.

Share of the dialed addresses that complete the handshake

Full screen V

Latency Over Time

Shows the response times of the online peers per transport. Select a metric:

Ping: the round trip time of a ping message.
Dial Time: the time to open the connection, including the Tor or I2P circuit.
Address Reply Time: the time from the getaddr request to the address reply.
Address Age: the median age of the addresses in the address replies.

Response times of the online peers per transport

Full screen V

Measurement Tools

Our network monitoring employs advanced crawling and probing tools and techniques to gather comprehensive data about network health, topology, and performance.