POST
/
2fc1de7f08c0465f6a28e3c355e0cb14
curl --request POST \
  --url https://base-mainnet.core.chainstack.com/2fc1de7f08c0465f6a28e3c355e0cb14 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_getBlockReceipts",
  "id": 1,
  "params": [
    "latest"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": [
    {
      "transactionHash": "<string>",
      "transactionIndex": 123,
      "blockHash": "<string>",
      "blockNumber": 123,
      "from": "<string>",
      "to": "<string>",
      "cumulativeGasUsed": 123,
      "gasUsed": 123,
      "contractAddress": "<string>",
      "logs": [
        {
          "removed": true,
          "logIndex": 123,
          "transactionIndex": 123,
          "transactionHash": "<string>",
          "blockHash": "<string>",
          "blockNumber": 123,
          "address": "<string>",
          "data": "<string>",
          "topics": [
            "<string>"
          ]
        }
      ],
      "status": "<string>"
    }
  ]
}

Base API method eth_getBlockReceipts retrieves all transaction receipts for a specified block. This method enables applications to access detailed information about every transaction within a block, including outcomes, gas used, and event logs.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • blockIdentifier — a string that specifies the block number in hexadecimal format or one of the strings "earliest", "latest", or "pending", indicating which block’s receipts to retrieve. For instance, using "latest" fetches the receipts for the most recent block.

​
Response

  • result — an array of objects, each representing a transaction receipt within the specified block. Key fields in each receipt include:
    • transactionHash — the hash of the transaction.
    • transactionIndex — the transaction’s index position within the block.
    • blockHash — the hash of the block containing the transaction.
    • blockNumber — the number of the block containing the transaction.
    • from — the address of the sender.
    • to — the address of the receiver (null for contract creation transactions).
    • cumulativeGasUsed — the total amount of gas used in the block up until this transaction.
    • gasUsed — the amount of gas used by this transaction.
    • contractAddress — the contract address created by the transaction, if any.
    • logs — an array of log objects generated by the transaction.
    • status — the status of the transaction (0x1 for success, 0x0 for failure).

​
Use case

The eth_getBlockReceipts method is crucial for applications requiring comprehensive transactional data from a block, such as:

  • Analyzing gas consumption and efficiency across transactions.
  • Monitoring smart contract interactions and logging for decentralized applications (DApps).
  • Verifying transaction execution outcomes for auditing and security analysis.

This method offers a granular view of block transactions, facilitating detailed analysis and monitoring of transaction outcomes, gas usage, and smart contract events on the Base blockchain.

Body

application/json

Response

200 - application/json
The transaction receipts of the block

The response is of type object.