Blockchain ExplorerInstall

Overview

The node "Blockchain Explorer" allows users to interact with multiple blockchain networks through their explorer APIs, which are compatible with Etherscan-like services. Specifically, the Account - Get Balance Multi operation fetches the native token balances for multiple blockchain addresses in a single request.

This operation is useful when you want to monitor or aggregate the balances of several wallet addresses across supported blockchains such as Ethereum, Binance Smart Chain, Polygon, Avalanche, and others. For example, a portfolio tracker could use this to display the combined balances of multiple user wallets on a selected network.

Properties

Output

The output JSON contains the following fields:

• network: The selected blockchain network.
• resource: Always "account" for this resource.
• operation: Always "getBalanceMulti" for this operation.
• Other fields returned by the blockchain explorer API, typically including:
  • status: API response status (e.g., "1" for success).
  • message: Response message (e.g., "OK").
  • result: An array of objects, each containing an address and its corresponding balance in the native token's smallest unit (e.g., wei for Ethereum).

Example snippet of the result field:

[
  {
    "account": "0x123...",
    "balance": "1000000000000000000"
  },
  {
    "account": "0x456...",
    "balance": "500000000000000000"
  }
]

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for a blockchain explorer service that supports Etherscan-compatible APIs.
• The node uses the Axios HTTP client to make requests to the explorer API.
• The base URL for the API depends on the selected network and environment configuration.
• Proper n8n credential setup is necessary to provide the API key.

Troubleshooting

• API Error: [message]: This error indicates that the blockchain explorer API returned an error response. Common causes include invalid API key, rate limiting, or malformed requests. Verify your API key and ensure the addresses are correctly formatted.
• Too many addresses: The operation supports a maximum of 20 addresses per request. Providing more than 20 may cause errors.
• Invalid address format: Ensure all addresses are valid blockchain addresses for the selected network.
• Network mismatch: Selecting a network that does not support the provided addresses can lead to empty or error responses.
• If the node fails but "Continue On Fail" is enabled, it will return an error object in the output JSON instead of stopping execution.

Links and References

• Etherscan API Documentation
• n8n Documentation on Creating Custom Nodes
• Axios HTTP Client