Chunk by Hash
chunk request type
This endpoint allows you to get a chunk by its hash on the NEAR blockchain.
Responses from the selected endpoint appear here after you run a request.
Live response output will appear here after you run a request.
Request reference
application/jsonThis operation accepts a JSON-RPC body over POST to /.
Required request inputs: yes
{
"jsonrpc": "2.0",
"id": "fastnear",
"method": "chunk",
"params": {
"chunk_id": "H6zcZFttQB82dDKUgZUcB3D7kU2TKCToujEu4dAmNtey"
}
}Request schema
jsonrpc *string2.0id *stringmethod *stringchunkparams *objectchunk_id *stringBase58-encoded chunk hash
Response reference
200 application/jsonSuccessful response
Response schema
jsonrpc *string2.0id *one ofresultobjectauthor *stringNEAR account ID
header *objectContains main info about the chunk.
balance_burnt *stringAmount in yoctoNEAR
bandwidth_requestsobjectnullableOne of multiple possible types
chunk_hash *stringBase58-encoded hash
congestion_infoobjectnullableStores the congestion level of a shard. More info about congestion [here](https://near.github.io/nearcore/architecture/how/receipt-congestion.html?highlight=congestion#receipt-congestion)
encoded_length *integerencoded_merkle_root *stringBase58-encoded hash
gas_limit *stringGas amount
gas_used *stringGas amount
height_created *integerheight_included *integeroutcome_root *stringBase58-encoded hash
outgoing_receipts_root *stringBase58-encoded hash
prev_block_hash *stringBase58-encoded hash
prev_state_root *stringBase58-encoded hash
rent_paidstringAmount in yoctoNEAR
shard_id *integerShard identifier
signature *stringBase58-encoded cryptographic signature
tx_root *stringBase58-encoded hash
validator_proposals *arrayitemsobjectvalidator_rewardstringAmount in yoctoNEAR
receipts *arrayitemsobjecttransactions *arrayitemsobjecterrorobjectcodeintegermessagestringdataobject