Blockchain Explorer icon

Blockchain Explorer

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

Actions22

Overview

The node interacts with multiple blockchain networks through their explorer APIs that are compatible with Etherscan. Specifically, for the Account resource and the Get Token Transfers operation, it retrieves a list of token transfer events associated with a specified blockchain address. This is useful for tracking token movements in and out of an account on various supported blockchains.

Common scenarios include:

  • Monitoring token transfers for wallet addresses to track asset inflows and outflows.
  • Auditing token transaction history for compliance or analysis.
  • Building dashboards or alerts based on token transfer activity.

Practical example:

  • A user wants to fetch recent token transfers for an Ethereum address to analyze token trading activity or verify receipt of tokens.

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 to query token transfers for (e.g., 0x...). Required.
Start Block Starting block number from which to begin fetching transactions. Use "0" for earliest block.
End Block Ending block number up to which to fetch transactions. Use "99999999" for latest block.
Page Page number for paginated results.
Offset Number of transactions to return per page (maximum 10,000).
Sort Sort order of returned transactions. Options: Ascending (asc), 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 "getTokenTx".
  • Other fields correspond to the API response from the blockchain explorer, typically including:
    • status: API call status.
    • message: Status message.
    • result: An array of token transfer event objects, each containing details such as:
      • blockNumber
      • timeStamp
      • hash (transaction hash)
      • from (sender address)
      • to (recipient address)
      • value (amount transferred)
      • tokenName
      • tokenSymbol
      • tokenDecimal
      • and other relevant token transfer metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the blockchain explorer service compatible with Etherscan APIs.
  • Uses the Axios HTTP client library internally to make API requests.
  • The node supports querying multiple blockchain networks; the base URL for the API depends on the selected network and environment.
  • No additional external dependencies beyond the configured API key and network selection.

Troubleshooting

  • API Errors: 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. Common causes include invalid addresses, rate limits exceeded, or incorrect API keys.
  • Invalid Address Format: Ensure the provided blockchain address is correctly formatted (e.g., starts with 0x for Ethereum-compatible chains).
  • Pagination Limits: The offset parameter has a maximum limit (10,000). Requesting more may cause errors or truncated results.
  • Network Selection: Selecting an unsupported or incorrect network may result in no data or errors.
  • Credential Issues: Missing or invalid API key credentials will prevent successful API calls.

To resolve errors:

  • Verify the correctness of input parameters.
  • Check API key validity and permissions.
  • Respect pagination limits.
  • Consult the blockchain explorer API documentation for specific error codes.

Links and References

Discussion