My node presently experiences:
$ bitcoin-cli getblockchaininfo
{
"chain": "predominant",
"blocks": 873668,
"headers": 873668,
"bestblockhash": "00000000000000000001b0251f80ba44e47217f661a06628f48eb71d659ce0eb",
"issue": 103919634711492.2,
"time": 1733586184,
"mediantime": 1733584532,
"verificationprogress": 0.9999971534840028,
"initialblockdownload": false,
"chainwork": "00000000000000000000000000000000000000009ef4d8bff5438c3689882eee",
"size_on_disk": 706175424632,
"pruned": false
}
size_on_disk “accounts for block information and undo information, and never for chainstate or any indexes you might have enabled on the block information” (H/T Pieter Wuille in feedback). 706,175,424,632 bytes translate to about 657.68 GiB. Solely the block information would possibly even be a little bit smaller, so 620 GiB may be that.
I don’t understand how bitinfocharts.com will get solely 490 GiB. They have to be utilizing a unique methodology, maybe they’re offering a sum of the overall serialized block information as an alternative of the scale of a node’s block information, however that’s only a guess.
Out of your supply at Statista.com:
Bitcoin’s blockchain measurement was near reaching 5450 gigabytes in 2024, because the database noticed exponential progress by almost one gigabyte each few days.
I do not know how they arrived at “5450 gigabytes”, and the blockchain doesn’t develop exponentially, it’s rising linearly at not more than 4 GiB per week. It may briefly develop sooner if the hashrate immediately will increase, however the issue adjustment would shortly right that.
