Actions113
- blocks Actions
- Get Block Details By Block Hash UTXOs
- List Transactions by Block Hash EVM
- List Transactions by Block Hash UTXOs
- List Transactions By Block Hash XRP
- List Transactions By Block Height XRP
- List Transactions by Block Height EVM
- List Transactions by Block Height UTXOs
- Get Block Details By Block Height UTXOs
- Get Block Details By Block Height EVM
- Get Block Details By Block Height XRP
- Get Block Details By Block Hash EVM
- Get Block Details By Block Hash XRP
- Get Last Mined Block EVM
- Get Last Mined Block UTXOs
- Get Latest Mined Block XRP
- List Latest Mined Blocks UTXOs
- List Latest Mined Blocks EVM
- List Latest Mined Blocks XRP
- HD Wallets Actions
- Sync HD Wallet (xPub, yPub, zPub)
- Derive And Sync New Receiving Addresses UTXO
- Derive And Sync New Change Addresses UTXO
- Derive And Sync New Receiving Addresses EVM
- Derive And Sync New Receiving Addresses XRP
- List Synced Addresses UTXO
- List Synced Addresses EVM
- List Synced Addresses XRP
- List HD Wallet (xPub, yPub, zPub) Transactions UTXO
- List HD Wallet (xPub, yPub, zPub) Transactions EVM
- List HD Wallet (xPub, yPub, zPub) Transactions XRP
- List HD Wallet (xPub, yPub, zPub) UTXOs
- Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub)
- Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM
- Get HD Wallet (xPub, yPub, zPub) Assets UTXO
- Get HD Wallet (xPub, yPub, zPub) Assets EVM
- Get HD Wallet (xPub, yPub, zPub) Assets XRP
- Get HD Wallet (xPub, yPub, zPub) Details UTXO
- Get HD Wallet (xPub, yPub, zPub) Details EVM
- Get HD Wallet (xPub, yPub, zPub) Details XRP
- List Synced HD Wallets (xPub, yPub, zPub)
- Activate HD Wallet (xPub, yPub, zPub)
- Delete Synced HD Wallet (xPub, yPub, zPub)
- address-latest Actions
- Utilities Actions
- simulate-transactions Actions
- addresses-latest Actions
- Get Address Balance Solana
- List Transactions By Address Solana
- Get Address Balance EVM
- Get Address Balance XRP
- Get Address Balance Kaspa
- List Confirmed Transactions By Address EVM
- List Transactions by Address XRP
- List Confirmed Transactions By Address UTXOs
- List Confirmed Transactions By Address Kaspa
- List Unconfirmed Transactions by Address UTXOs
- List Internal Transactions By Address EVM
- Get Next Available Nonce EVM
- List Confirmed Tokens Transfers By Address EVM
- addresses-historical Actions
- Get Address Balance UTXOs
- List Confirmed Transactions By Address EVM history
- List Confirmed Transactions By Address UTXO Historical
- List Unspent Transaction Outputs By Address UTXOs
- Sync Address
- List Synced Addresses
- Get Synced Address Tokens Transfer EVM
- Activate Synced Address
- Delete Synced Address
- List Synced Address Internal Transactions EVM
- List Tokens By Address Synced EVM
- blockchain-events Actions
- New Confirmed Coins Transactions
- New Unconfirmed Coins Transactions
- New Confirmed Tokens Transactions
- New Confirmed Coins Transactions And Each Confirmation
- New Confirmed Tokens Transactions And Each Confirmation
- Mined Transaction
- New Block
- List Blockchain Events Subscriptions
- Get Blockchain Event Subscription Details By Reference ID
- Delete Blockchain Event Subscription
- Activate Blockchain Event Subscription
- New Confirmed Internal Transactions
- New Confirmed Internal Transactions And Each Confirmation
- Crypto Transactions Actions
- Get Transaction Details By Transaction Hash Solana
- Get Transaction Details By Transaction Id Kaspa
- Get Transaction Details By Transaction Hash EVM
- Get Transaction Details By Transaction Hash UTXOs
- Get Transaction Details By Transaction Hash XRP
- List Internal Transaction Details by Transaction Hash EVM
- List Tokens Transfers By Transaction Hash EVM
- List Logs By Transaction Hash EVM
- Get Raw Transaction Data UTXOs
- contracts Actions
- blockchain-fees Actions
- broadcast-transactions Actions
- prepare-transactions Actions
- Market Data & Prices Actions
Overview
This node interacts with the Crypto APIs REST API to list internal transactions for a synced address on an EVM-compatible blockchain. It is designed to retrieve historical internal transaction data related to a specific wallet address, filtered by blockchain and network parameters.
Common scenarios where this node is beneficial include:
- Auditing or monitoring internal transactions of a wallet address on blockchains like Ethereum.
- Gathering detailed transaction history for analytics or reporting purposes.
- Integrating blockchain transaction data into workflows for compliance or accounting.
For example, you can use this node to fetch all internal transactions associated with a given Ethereum address on the mainnet, optionally limiting the number of results or sorting them in ascending/descending order.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to query (e.g., Ethereum, Binance Smart Chain). |
| network | The specific network within the blockchain (e.g., mainnet, testnet). |
| address | The wallet address whose internal transactions are to be listed. |
| context | Optional context string to correlate requests or responses. |
| limit | Optional maximum number of records to return. |
| sortingOrder | Optional order to sort the results, typically ascending or descending. |
| startingAfter | Optional cursor for pagination to start listing after a specific transaction ID. |
Output
The node outputs an array of JSON objects representing internal transactions related to the specified address. Each object contains details about a single internal transaction as returned by the Crypto APIs service.
If binary data were involved (not indicated here), it would represent associated files or media, but this operation focuses solely on JSON transaction data.
Dependencies
- Requires an active connection to the Crypto APIs REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The node reads a local OpenAPI specification file (
2024-12-12-final.json) bundled with the node to dynamically build requests.
Troubleshooting
- Operation not found error: If the specified operation cannot be found, ensure that the "List Synced Address Internal Transactions EVM" operation is correctly selected and that the node's bundled OpenAPI spec file is intact.
- Invalid or missing parameters: Required fields such as
blockchain,network, andaddressmust be provided; otherwise, the API call will fail. - API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Pagination issues: When using
startingAfter, ensure the value corresponds to a valid transaction ID from a previous response to avoid empty results.
Links and References
- Crypto APIs Documentation
- EVM Internal Transactions API Reference (for detailed parameter and response schema)