Blockchain Explorer
Actions22
- Account Actions
- Block Actions
- Contract Actions
- Gas Actions
- Stat Actions
- Token Actions
- Transaction Actions
Overview
This node interacts with multiple blockchain networks through their explorer APIs that are compatible with Etherscan. Specifically, the "Get Token Info" operation under the "Token" resource fetches detailed information about a token by querying its contract address on a selected blockchain network.
Common scenarios where this node is beneficial include:
- Retrieving metadata about a specific token such as name, symbol, decimals, and total supply.
- Integrating token details into dashboards or reports.
- Validating token contract addresses before processing transactions or balances.
For example, you can use this node to get token info for an ERC-20 token on Ethereum or a BEP-20 token on Binance Smart Chain by providing the respective contract address and selecting the appropriate 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. |
| Contract Address | The contract address of the token to query. This must be a valid blockchain contract address (e.g., 0x...). |
Output
The output JSON contains the following fields:
network: The blockchain network used for the query.resource: The resource type, here it will be"token".operation: The operation performed, here"getTokenInfo".- Additional data fields returned by the blockchain explorer API related to the token information. These typically include token metadata such as:
- Token name
- Symbol
- Decimals
- Total supply
- Other token-specific details provided by the explorer API
If the API returns an error, the node outputs an error message in the JSON under the error field.
The node does not output binary data.
Dependencies
- Requires an API key credential for accessing the blockchain explorer API service.
- Supports multiple blockchain networks via their respective explorer APIs.
- No additional environment variables are required beyond the API key credential configuration.
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 contract addresses, unsupported networks, or rate limiting.
- Invalid Contract Address: Ensure the contract address is correctly formatted and corresponds to the selected network.
- Network Mismatch: Selecting a network different from the one where the token contract is deployed will result in errors or empty responses.
- Credential Issues: Make sure the API key credential is valid and has sufficient permissions/quota.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, outputting error messages per item.
Links and References
- Etherscan API Documentation
- BscScan API Documentation
- PolygonScan API Documentation
- General info on ERC-20 tokens: https://ethereum.org/en/developers/docs/standards/tokens/erc-20/
This summary is based solely on static analysis of the provided source code and property definitions.