Chunks are subdivisions of blocks in NEAR’s sharded architecture. Each chunk contains a subset of the transactions and receipts for a particular shard, facilitating parallel processing and scalability. Chunks are identified by a hash and are associated with a specific block.

Table Columns

Column NameDescription
balance_burntThe number of tokens burnt
block_hashThe hash of the block
block_heightThe height of the block
block_timestampThe time at which the block was created/added to the chain
chunk_hashThe hash of the chunk
encoded_lengthThe chunk length encoded in integer format
encoded_merkle_rootThe encoded merkle root
gas_limitThe maximum gas allowed in this block
gas_usedThe total used gas by all transactions in this block
height_createdThe chunk height created
height_includedThe included height of the chunk
outcome_rootThe root of the outcome trie of the block
outgoing_receipts_rootThe root of the outgoing receipts of the block
prev_block_hashThe hash of the previous block chunk corresponding to the current one
prev_state_rootThe previous state of the root of the corresponding block
receipt_countThe number of receipts in this chunk
rent_paidThe number of tokens paid as rent
shard_idThe id of the multiple data grouped together
signatureThe standard ed25519 signature type
transactions_countThe number of transactions in this chunk
tx_rootThe transaction root
validator_proposalsAn array of proposals provided by the validators
validator_rewardThe reward sent to the validators
includedWhether this chunk is included in the parent block or not (height_included == block_height)
_created_atTimestamp of the entry creation
_updated_atTimestamp of the entry update