Blockchain Explorer
Actions22
- Account Actions
- Block Actions
- Contract Actions
- Gas Actions
- Stat Actions
- Token Actions
- Transaction Actions
Overview
The node interacts with multiple blockchain networks through their explorer APIs that are compatible with Etherscan. Specifically, for the Account resource and the Get Internal Transactions operation, it retrieves a list of internal transactions associated with a specified blockchain address. Internal transactions represent value transfers or contract calls that occur within a transaction but are not recorded as standalone transactions on the blockchain.
This node is beneficial when you want to analyze detailed activity related to an account beyond normal transactions, such as tracing contract interactions or internal token movements. For example, developers or analysts can use it to audit smart contract behavior or track funds flow inside complex decentralized applications.
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. |
| Address | The blockchain address to query internal transactions for. Must be a valid address string (e.g., "0x..."). Required. |
| Start Block | Starting block number from which to begin the search. Use "0" for the earliest block. |
| End Block | Ending block number up to which to search. Use "99999999" for the latest block. |
| Page | Page number for pagination of results. |
| Offset | Number of transactions to return per page. Maximum is 10,000. |
| Sort | Sort order of the returned transactions. Options: Ascending ("asc") or Descending ("desc"). |
Output
The output JSON contains the following fields:
network: The blockchain network queried.resource: The resource type, here always"account".operation: The operation performed, here"getInternalTxs".- Additional data fields returned by the blockchain explorer API, including:
status: Status code of the API response.message: Message describing the API response status.result: An array of internal transaction objects, each typically containing details such as block number, timestamp, from/to addresses, value transferred, gas used, input data, and transaction hash.
The node outputs one item per input, pairing the original input index with the corresponding result.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the blockchain explorer service compatible with Etherscan APIs.
- Uses the Axios HTTP client library internally to make REST API requests.
- The node supports querying multiple blockchain networks; the base URL for the API depends on the selected network and environment.
- Proper configuration of the API key credential in n8n is necessary for successful authentication.
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. This often indicates invalid parameters, rate limiting, or issues with the API key. - Invalid Address: Providing an incorrectly formatted blockchain address will likely cause the API to fail or return no results.
- Pagination Limits: Requesting too many transactions at once (offset > 10000) may cause errors or truncated results.
- Network Mismatch: Selecting a network that does not support the requested operation or address format may lead to errors.
- To resolve errors, verify the correctness of all input parameters, ensure the API key is valid and has sufficient permissions, and check the network compatibility.