Blockchain ExplorerInstall

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 Receipt operation, it retrieves detailed information about a specific transaction on a selected blockchain network by querying the transaction receipt using its hash.

This is useful when you want to verify the outcome of a blockchain transaction, check logs emitted by smart contracts during the transaction, or get metadata such as gas used, status, and block confirmations.

Practical examples:

• After submitting a transaction to Ethereum or Polygon, use this node to confirm if the transaction was successful.
• Retrieve event logs from a contract interaction to trigger further automation based on emitted events.
• Monitor transaction receipts across different supported networks like Binance Smart Chain or Avalanche.

Properties

Output

The output JSON contains the following fields:

• network: The blockchain network queried (e.g., ethereum).
• resource: The resource type, here always "transaction".
• operation: The operation performed, here "getTxReceipt".
• Other fields returned by the blockchain explorer API corresponding to the transaction receipt details, which typically include:
  • Status of the transaction (success/failure).
  • Block number where the transaction was included.
  • Gas used and cumulative gas used.
  • Contract address created (if any).
  • Logs generated by the transaction.
  • Transaction hash and other metadata.

The node does not output binary data.

Dependencies

• Requires an API key credential for a blockchain explorer service compatible with Etherscan APIs.
• Supports multiple blockchain networks; the base URL for the API depends on the selected network and environment.
• Uses the Axios HTTP client library internally to make API requests.

Troubleshooting

• Common issues:

  • Invalid or missing transaction hash will cause the API to return an error.
  • Using an incorrect network for the given transaction hash may result in no data or errors.
  • API rate limits or invalid API keys can cause request failures.

• Error messages:

  • API Error: ... indicates the blockchain explorer API returned an error message. Check the transaction hash validity, network selection, and API key permissions.
  • Network connectivity issues or timeouts may also cause errors; ensure stable internet connection.

• Resolution tips:

  • Verify the transaction hash format and correctness.
  • Confirm the selected network matches the blockchain where the transaction was submitted.
  • Ensure the API key credential is valid and has sufficient quota.
  • Enable "Continue On Fail" option in the node settings to handle errors gracefully in workflows.

Links and References

• Etherscan API Documentation
• Blockchain Explorer APIs Compatible with Etherscan
• n8n Documentation on Creating Custom Nodes