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 Contract - Get ABI operation, it retrieves the Application Binary Interface (ABI) of a verified smart contract given its address on a selected blockchain network. The ABI is essential for interacting programmatically with smart contracts, such as calling functions or decoding events.

Common scenarios where this node is beneficial include:

  • Developers needing to fetch the ABI of a deployed contract to interact with it in their applications.
  • Auditors or analysts verifying contract interfaces.
  • Automation workflows that require contract metadata for further processing or integration.

For example, you can use this node to get the ABI of a token contract on Ethereum or Polygon to decode transaction data or call contract methods dynamically.

Properties

Name Meaning
Network The blockchain network to query. Options: Arbitrum, Avalanche, Binance Smart Chain, Celo, Cronos, Ethereum, Fantom, Moonbeam, Optimism, Polygon.
Contract Address The address of the smart contract whose ABI you want to retrieve. Must be a valid contract address on the selected network.

Output

The output JSON contains the following fields:

  • network: The blockchain network queried.
  • resource: The resource type, here always "contract".
  • operation: The operation performed, here "getAbi".
  • Additional fields returned by the blockchain explorer API, typically including:
    • status: Status code of the API response.
    • message: Response message from the API.
    • result: The actual ABI data as a JSON string or array describing the contract's interface.

The node outputs the ABI information in the json field of the item, which can then be used downstream in the workflow for contract interaction or analysis.

Dependencies

  • Requires an API key credential for a blockchain explorer service compatible with Etherscan APIs.
  • The node supports multiple blockchain networks; the correct network must be selected.
  • No additional external dependencies beyond the configured API credential and network selection.

Troubleshooting

  • API Error: If the contract address is invalid, unverified, or the API key quota is exceeded, the node will throw an error with the message from the API. Verify the contract address and ensure the contract is verified on the explorer.
  • Empty or Missing ABI: If the contract is not verified on the selected network’s explorer, the ABI will not be available. Confirm contract verification status on the blockchain explorer website.
  • Network Mismatch: Ensure the selected network matches the contract’s deployment network; otherwise, no data or errors may occur.
  • Credential Issues: Make sure the API key credential is correctly set up and has sufficient permissions/quota.

Links and References

Discussion