<blockquote>
  <p>This Serialized data doesn't contain certain fields like <code>confirmations</code>, <code>chainwork</code> <code>nextblockhash</code>. Is there any reason for this?</p>
</blockquote>

<p>Those fields are not actually part of a block and cannot be contained in a block.</p>

<p>The number of confirmations for a block constantly changes as more blocks are found on top of that block. Thus it cannot be part of a block in the serialized data.</p>

<p>The chainwork does not need to be included in a block because it can be dynamically calculated, unlike the other data in a block.</p>

<p>The <code>nextblockhash</code> cannot be known at the time of creation for a block because miners can't see the future. The <code>nextblockhash</code> cannot be known wihtout the current block already existing.</p>

CC BY-SA 4.0
2018-05-24T04:35:33.420Z
2018-05-24T04:35:33.420Z
Ava Chow
<p><code>bitcoin-cli getblock 000000000003b9c88b8a4bf0bac7059913381bba300cdfddffc54a3d8c6e8105 false</code></p>

<p>This command will give block related data in the form of Hex. This Serialized data doesn't contain certain fields like <code>confirmations</code>, <code>chainwork</code> <code>nextblockhash</code>. Is there any reason for this?</p>

<block><bitcoin-cli>
Serialized Block doesn't have all the fields of a Block
lch
# Serialized Block doesn't have all the fields of a Block

(Asked by: username_0 on 2018-05-24)

`bitcoin-cli getblock 000000000003b9c88b8a4bf0bac7059913381bba300cdfddffc54a3d8c6e8105 false`

This command will give block related data in the form of Hex. This Serialized data doesn't contain certain fields like `confirmations`, `chainwork` `nextblockhash`. Is there any reason for this?

**Tags:** block, bitcoin-cli


---

## 1 answers

### Answer by username_1 on 2018-05-24. Score: 3 | Accepted answer

> This Serialized data doesn't contain certain fields like `confirmations`, `chainwork` `nextblockhash`. Is there any reason for this?

Those fields are not actually part of a block and cannot be contained in a block.

The number of confirmations for a block constantly changes as more blocks are found on top of that block. Thus it cannot be part of a block in the serialized data.

The chainwork does not need to be included in a block because it can be dynamically calculated, unlike the other data in a block.

The `nextblockhash` cannot be known at the time of creation for a block because miners can't see the future. The `nextblockhash` cannot be known wihtout the current block already existing.


---

