It would be useful to convey some of the blockhash to the run the numbers panel as a means of verifying that it was a result from running, vs an expected total sum that can be precomputed.
From this JSON
{
"height": 659850,
"bestblock": "00000000000000000009b169c0b9738c3e6d9d7c09b48520c65c2fc09ecf63be",
"transactions": 42237837,
"txouts": 68460153,
"bogosize": 5139018165,
"hash_serialized_2": "94260bb47f9b8ba789ce797d7b792bd5ebd66a30f9220ad5c9e6c70593fad820",
"disk_size": 4165819865,
"total_amount": 18561377.69332505
}The bestblock hash is too long to display in its entirety, but could have a shortened representation as 9b169c..cf63be being the first 6 hexadecimal characters after the leading 0s and the last 6 at the end.
It would be useful to convey some of the blockhash to the run the numbers panel as a means of verifying that it was a result from running, vs an expected total sum that can be precomputed.
From this JSON
{ "height": 659850, "bestblock": "00000000000000000009b169c0b9738c3e6d9d7c09b48520c65c2fc09ecf63be", "transactions": 42237837, "txouts": 68460153, "bogosize": 5139018165, "hash_serialized_2": "94260bb47f9b8ba789ce797d7b792bd5ebd66a30f9220ad5c9e6c70593fad820", "disk_size": 4165819865, "total_amount": 18561377.69332505 }The bestblock hash is too long to display in its entirety, but could have a shortened representation as
9b169c..cf63bebeing the first 6 hexadecimal characters after the leading 0s and the last 6 at the end.