Bitcoin Core getchaintxstats RPC: Chain Activity Guide

This guide explains Bitcoin Core getchaintxstats RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Window arguments

nblocks selects the intended window and defaults to roughly one month in blocks. A supplied blockhash anchors the end; otherwise the current active tip is used. Validate positive integer bounds and record the resolved ending hash because an unanchored query can change between runs or after a reorganisation.

Returned counts

txcount is cumulative transactions through the ending block, while window_tx_count covers the selected interval. Window_block_count reports the actual number used and can be smaller near genesis. Do not subtract independently sampled cumulative counts unless their block identities and ancestry have also been verified.

Elapsed time and rate

window_interval is the difference between boundary block timestamps and txrate is the average transaction count per second over that interval. Miner-selected timestamps are consensus constrained but not precise wall-clock measurements. Short windows can be highly noisy and an interval of zero suppresses the rate field.

What the rate excludes

The statistic counts confirmed transactions, not inputs, outputs, value transferred, fee demand, virtual bytes or rejected transactions. Batching can increase economic activity while reducing transaction count. Capacity planning should add block weight, fee rates, mempool composition and application-specific settlement data.

Reorganisations and history

A recent ending hash can leave the active chain. Store the ending hash, height, chainwork and observation time, then recompute affected windows after a reorganisation. Historical comparisons should use stable buried anchors and preserve the original result rather than silently rewriting an operational report.

Monitoring design

Use several windows to distinguish short bursts from sustained change. Align comparisons by exact block boundaries and expose sample length, not just txrate. Alert on missing fields, implausible intervals and node lag. Never interpret a responsive statistic as evidence that the node is fully synced.

How specialists test it

Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.

Conclusion

getchaintxstats provides a reproducible view of confirmed chain activity when its boundary and assumptions are retained. It cannot by itself measure demand, value, capacity or node health.