Team CryptoInsightfull 
My node currently reports:
$ bitcoin-cli getblockchaininfo
{
"chain": "main",
"blocks": 873668,
"headers": 873668,
"bestblockhash": "00000000000000000001b0251f80ba44e47217f661a06628f48eb71d659ce0eb",
"difficulty": 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 files and undo data, and not for chainstate or any indexes you may have enabled on the block data” (H/T Pieter Wuille in comments). 706,175,424,632 bytes translate to about 657.68 GiB. Only the block data might even be a little smaller, so 620 GiB might be that.
I don’t know how bitinfocharts.com gets only 490 GiB. They must be using a different methodology, perhaps they are providing a sum of the total serialized block data instead of the size of a node’s block files, but that’s just a guess.
From your source at Statista.com:
Bitcoin’s blockchain size was close to reaching 5450 gigabytes in 2024, as the database saw exponential growth by nearly one gigabyte every few days.
I have no idea how they arrived at “5450 gigabytes”, and the blockchain does not grow exponentially, it is growing linearly at no more than 4 GiB per week. It could briefly grow faster if the hashrate suddenly increases, but the difficulty adjustment would quickly correct that.
