Nodes

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 48 blocks counts as in sync.

• In Sync: at most 48 blocks from the majority tip.
• Behind and Far Behind: more than 48 and more than 4,032 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 48 blocks above the majority tip. Such nodes follow another chain.
• Height 0: the node reports no blocks.

Sync State

Shows the values of the latest crawl.

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 48 blocks counts as in sync.

• In Sync: at most 48 blocks from the majority tip.
• Behind and Far Behind: more than 48 and more than 4,032 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 48 blocks above the majority tip. Such nodes follow another chain.
• Height 0: the node reports no blocks.

Feature Adoption Over Time

Shows the online peers that support a feature. The dashed line shows all online peers. Select a transport to compare, for example, Tor and I2P nodes with IPv4 nodes.

• BIP324 v2 Transport, Segwit, Compact Filters, and Bloom Filters: the service flags NODE_P2P_V2, NODE_WITNESS, NODE_COMPACT_FILTERS, and NODE_BLOOM.
• Pruned: NODE_NETWORK_LIMITED without NODE_NETWORK. The node keeps only the recent blocks.
• Blocks Only: the node does not relay transactions (relay flag false).
• addrv2, wtxidrelay, and Erlay: the node sent sendaddrv2, wtxidrelay, or sendtxrcncl.

Feature Adoption

Shows the values of the latest crawl.

Shows the online peers that support a feature. The dashed line shows all online peers. Select a transport to compare, for example, Tor and I2P nodes with IPv4 nodes.

• BIP324 v2 Transport, Segwit, Compact Filters, and Bloom Filters: the service flags NODE_P2P_V2, NODE_WITNESS, NODE_COMPACT_FILTERS, and NODE_BLOOM.
• Pruned: NODE_NETWORK_LIMITED without NODE_NETWORK. The node keeps only the recent blocks.
• Blocks Only: the node does not relay transactions (relay flag false).
• addrv2, wtxidrelay, and Erlay: the node sent sendaddrv2, wtxidrelay, or sendtxrcncl.

Signal Bits Over Time

Shows the online peers that set a service bit from bit 12 upwards in their version message. The dashed line shows all online peers. BIPs assign the bits 0 to 11. Clients use the higher bits for experiments and to signal their policy, for example Bitcoin Knots sets the bits 26 to 28. Select an agent type to see how many of its nodes set a bit.

Signal Bits

Shows the values of the latest crawl.

Shows the online peers that set a service bit from bit 12 upwards in their version message. The dashed line shows all online peers. BIPs assign the bits 0 to 11. Clients use the higher bits for experiments and to signal their policy, for example Bitcoin Knots sets the bits 26 to 28. Select an agent type to see how many of its nodes set a bit.

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.

Suspected Fleets

Shows the values of the latest crawl.

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.

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.

Address Replies

Shows the values of the latest crawl.

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.

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.

Clock Offset

Shows the values of the latest crawl.

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.

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.