Returns full transaction details for all transactions in a block. Unlike getBlockTransactions, this includes complete transaction data with messages, fees, and state changes. Useful for block explorers and indexers that need to process entire blocks.
The workchain to query. Use -1 for masterchain (validators, system contracts, config) or 0 for basechain (regular accounts and contracts). Most user transactions happen on workchain 0.
The shard identifier. Masterchain always uses -9223372036854775808. For basechain, shards split and merge dynamically. Use the shards endpoint to discover current shard configuration.
The block sequence number. Each shard numbers its blocks starting from 0. For masterchain, this is also called the block height. Higher numbers are more recent blocks.
The block's root hash for verification. Together with file_hash, this uniquely and cryptographically identifies a block. Only needed when you require proof of block identity.
The block's file hash for verification. Together with root_hash, this provides cryptographic proof of block identity. Only needed for trustless verification.
Pagination cursor. Pass the lt value from the last item in your previous response to get the next page. Transactions and messages are ordered by logical time.
Secondary pagination cursor for block transactions. When multiple accounts have transactions at the same lt, use this to continue from a specific account.
Maximum number of items to return. The default is 40. Use smaller values for faster responses or larger values to reduce the number of API calls.
OK
Response containing detailed transactions from a block.
Indicates if the request succeeded. If false, check the error field for details.
The response data. Only present when ok is true.
Optional request ID that you can pass in the request and receive back in the response. Useful for matching async responses.