Blockchain Explorer icon

Blockchain Explorer

Interact with multiple blockchain networks via their explorer APIs (Etherscan-compatible)
Join our community

Actions22

Overview

This node interacts with multiple blockchain networks through their explorer APIs that are compatible with Etherscan. Specifically, the Get Block Reward operation under the Block resource fetches the block and uncle rewards for a specified block number on a chosen blockchain network.

This node is useful when you want to retrieve detailed reward information about a particular block on popular blockchains such as Ethereum, Binance Smart Chain, Polygon, Avalanche, and others supported by Etherscan-compatible explorers.

Practical examples:

  • Fetching the mining rewards for a specific Ethereum block to analyze miner incentives.
  • Retrieving block reward data on Binance Smart Chain to monitor network economics.
  • Comparing uncle rewards across different blocks on Polygon or Fantom networks.

Properties

Name Meaning
Network The blockchain network to query. Options include Arbitrum, Avalanche, Binance Smart Chain, Celo, Cronos, Ethereum, Fantom, Moonbeam, Optimism, and Polygon.
Block Number The specific block number to query for its reward details. Must be provided as a string representing the block height (e.g., "12345678").

Output

The output JSON contains the following fields:

  • network: The selected blockchain network.
  • resource: Always "block" for this operation.
  • operation: Always "getBlockReward" for this operation.
  • Other fields returned by the blockchain explorer API, typically including:
    • Block reward details such as miner rewards, uncle rewards, and possibly other metadata related to the block's reward distribution.
    • Status and message fields indicating success or failure of the API call.

The exact structure depends on the underlying blockchain explorer API response but generally includes comprehensive reward information for the requested block.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for accessing the blockchain explorer API service.
  • Supports multiple blockchain networks via their respective Etherscan-compatible explorer APIs.
  • No additional environment variables are required beyond the configured API key credential.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Querying a block number that does not exist or is out of range for the selected network may return errors.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • "API Error: <message>" indicates the blockchain explorer API returned an error. The message usually explains the cause, such as invalid parameters or rate limiting.
    • If the node throws an error about missing parameters, ensure the block number and network are correctly set.

  • Resolutions:

    • Verify the API key is valid and has sufficient permissions.
    • Confirm the block number exists on the chosen network.
    • Check internet connectivity and API endpoint accessibility.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion