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 Transaction resource and the Get Transaction Status operation, it retrieves the execution status of a blockchain transaction given its hash. This is useful to verify whether a transaction was successful, failed, or is still pending on supported blockchains.

Common scenarios include:

  • Monitoring the status of a submitted transaction to confirm if it has been mined successfully.
  • Automating workflows that depend on transaction confirmation before proceeding.
  • Debugging or auditing blockchain transactions by checking their final state.

Example: After sending a payment or token transfer on Ethereum or Polygon, you can use this node to check if the transaction succeeded by providing the transaction hash and network.

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.
Transaction Hash The unique hash identifier of the transaction to query. Required string input (e.g., "0x...").

Output

The output JSON contains the following fields:

  • network: The blockchain network queried.
  • resource: Always "transaction" for this operation.
  • operation: Always "getTxReceiptStatus" for this operation.
  • Other fields returned by the blockchain explorer API, typically including:
    • status: A string indicating success ("1") or failure ("0").
    • message: Status message from the API (e.g., "OK" or error description).
    • result: Detailed information about the transaction status, such as whether it was successful or failed.

The node outputs one item per input, pairing the response with the original input index.

No binary data is output 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.
  • No additional environment variables are required beyond the configured API key credential.
  • Supported blockchain networks must be selected explicitly.

Troubleshooting

  • API Error: ... — Indicates the blockchain explorer API returned an error. Common causes:

    • Invalid or missing transaction hash.
    • Unsupported network or incorrect network selection.
    • API key issues such as quota exceeded or invalid credentials.

    Resolution: Verify the transaction hash format, ensure the correct network is selected, and confirm the API key is valid and has sufficient permissions.

  • Timeouts or network errors — Could occur due to connectivity issues or rate limiting by the API provider.

    Resolution: Check internet connection, retry after some time, or upgrade API plan if rate limits are hit.

  • If the node returns empty or unexpected results, confirm the transaction hash exists on the selected network and that the transaction has been mined.

Links and References

Discussion