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, for the Account resource and the Get Normal Transactions operation, it retrieves a list of normal (external) transactions associated with a specified blockchain address.

This is useful when you want to analyze or monitor the transaction history of an account on various supported blockchains such as Ethereum, Polygon, Binance Smart Chain, Avalanche, and others. For example, you can use this node to fetch recent transactions sent or received by a wallet address to track activity, audit transfers, or feed data into further workflows like notifications or analytics.

Properties

Name Meaning
Network The blockchain network to query. Options: Arbitrum, Avalanche, Binance Smart Chain, Celo, Cronos, Ethereum, Fantom, Moonbeam, Optimism, Polygon. Default is Ethereum.
Address The blockchain address whose normal transactions you want to retrieve. Must be a valid address string starting with "0x...".
Start Block Starting block number from which to begin fetching transactions. Use "0" for the earliest block.
End Block Ending block number up to which to fetch transactions. Use "99999999" for the latest block.
Page Page number for paginated results. Useful for navigating through large sets of transactions.
Offset Number of transactions to return per page. Maximum allowed is 10,000.
Sort Sort order of the returned transactions. Options: Ascending (asc) or Descending (desc). Default is Ascending.

Output

The output JSON contains the following fields:

  • network: The blockchain network queried.
  • resource: The resource type, here always "account".
  • operation: The operation performed, here "getNormalTxs".
  • Other fields correspond to the API response from the blockchain explorer, typically including:
    • status: Status code of the API response.
    • message: Response message.
    • result: An array of transaction objects, each representing a normal transaction involving the specified address. Each transaction object usually includes details such as:
      • blockNumber
      • timeStamp
      • hash (transaction hash)
      • nonce
      • blockHash
      • transactionIndex
      • from (sender address)
      • to (recipient address)
      • value (amount transferred)
      • gas
      • gasPrice
      • isError (indicates if the transaction failed)
      • txreceipt_status
      • and other relevant transaction metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for a blockchain explorer service compatible with Etherscan APIs.
  • The node uses Axios HTTP client internally to make requests to the explorer API.
  • No additional environment variables are required beyond the configured API key credential.
  • Supported blockchain networks are predefined and must be selected accordingly.

Troubleshooting

  • API Error: If the API returns a status of "0" with a message other than "OK", the node throws an error with the API's error message. This often indicates invalid parameters, rate limiting, or issues with the API key.

    • Resolution: Verify the correctness of the input parameters (address format, block numbers), ensure the API key is valid and has sufficient quota, and check network availability.

  • Invalid Address: Providing an incorrectly formatted blockchain address will result in API errors or empty results.

    • Resolution: Ensure the address is a valid hexadecimal string starting with "0x".

  • Pagination Issues: Requesting pages beyond available data may return empty results.

    • Resolution: Adjust the Page and Offset parameters according to expected transaction volume.

  • Rate Limits: Excessive requests may trigger rate limits from the blockchain explorer API.

    • Resolution: Implement delays between requests or upgrade API plan if applicable.

Links and References

Discussion