eth_getBlockByHash - Ethereum
Recalls the data about a block by hash
How to Use the eth_getBlockByHash Method
Parameters
DATA, 32 Bytes - Block’s hash.
Boolean - In true cases – presents the full objects of a transaction. In false cases – recalls transactions’ hashes.
What you receive
Object - A block object with all the fields below, or null if the block cannot be found:
number: QUANTITY - the number of a block. in case of a pending block, it returns null.
hash: DATA, 32 Bytes - block’s hash. in case of a pending block, it returns null.
parentHash: DATA, 32 Bytes - parent block’s hash.
nonce: DATA, 8 Bytes - the generated proof-of-work’s hash. in case of a pending block, it returns null.
sha3Uncles: DATA, 32 Bytes - he uncles data’s SHA3.
logsBloom: DATA, 256 Bytes - the logs of the block’s bloom filter. in case of a pending block, it returns null.
transactionsRoot: DATA, 32 Bytes - the transaction trie’s root.
stateRoot: DATA, 32 Bytes - the final state trie’s root.
receiptsRoot: DATA, 32 Bytes - the receipts trie’s root.
miner: DATA, 20 Bytes - the beneficiary's address that you are sending mining rewards to.
difficulty: QUANTITY - block’s difficulty level presented as an integer.
totalDifficulty: QUANTITY - the total chain’s difficulty level up tol this block presented as an integer.
extraData: DATA - a field for additional data in this block.
size: QUANTITY - integer the size of this block in bytes.
gasLimit: QUANTITY - the maximum amount of gas which is suitable in this block.
gasUsed: QUANTITY - the total amount of gas used for transactions in this block.
timestamp: QUANTITY - the collation time of the block presented as a unix timestamp.
transactions: Array - Array that includes objects for transactions, or 32 Bytes transaction hashes that depends on the last parameter you give.
uncles: Array - Array consisting of uncle hashes.
Sample
Here is a typical appliance example.
Call
Outcome
Last updated