Chain Size Growth
Total blockchain size over time, showing how fast the chain is growing
Short ranges plot one point per block, about one every ten minutes. Longer ranges plot one point per day, computed from every block in that day. How it is computed depends on the chart: some average, some total the day up, some are a ratio of the day's sums, and each chart says which. Either way a brief spike inside a day is smoothed away.
Get this data
About this metric
Definition
The total size of the blockchain on disk, back to 2009. What makes a node trustless is that it checked every one of those blocks itself, not that it still has them: an archival node keeps them all, while a pruned node verifies each block as it arrives and then discards the old ones, keeping a few gigabytes. So this is the floor for archiving the chain, not the price of running a node.
How it is measured
Two lines, measuring two different things. Block Data is the blocks themselves, summed across the range and added to the stored total for everything before it. That is block bytes alone: it excludes the chainstate and index databases a node also keeps, so a full data directory is larger than this line.
Disk Size is that same series scaled by one ratio, what my node reports on disk today divided by its block data today, which is how the chainstate, the indexes and the undo files enter the chart. Only today's point of it is measured; every earlier point assumes those extras have always been the same fraction of block data, and they have not, because the unspent-output set grows on its own terms. So read the gap between the two lines as roughly what a node keeps beyond the blocks, not as a reconstruction of any past day's disk usage.
A pruned node stores a fraction of either line and still verifies everything.
Measured from my own Bitcoin node. Methodology