Block

Get a Block

Changed on

Get a block by its Block Identifier. If transactions are returned in the same call to the node as fetching the block, the response should include these transactions in the Block object. If not, an array of Transaction Identifiers should be returned so /block/transaction fetches can be done to get all transaction information.

When requesting a block by the hash component of the BlockIdentifier, this request MUST be idempotent: repeated invocations for the same hash-identified block must return the exact same block contents.

No such restriction is imposed when requesting a block by height, given that a chain reorg event might cause the specific block at height n to be set to a different one.

post/block

Request

  • The document declares no server URL.
  • Auth: none declared

Request body

network_identifierNetworkIdentifier required(unresolved $ref)
block_identifierPartialBlockIdentifier required(unresolved $ref)

Response

Expected response to a valid request

blockBlock (unresolved $ref)
other_transactionsTransactionIdentifier[] (unresolved $ref)

Some blockchains may require additional transactions to be fetched that weren't returned in the block response (ex: block only returns transaction hashes). For blockchains with a lot of transactions in each block, this can be very useful as consumers can concurrently fetch all transactions returned.

Changes