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 by a specific address on an EVM-compatible blockchain. It is useful for users who want to retrieve detailed information about internal transactions (transactions triggered within smart contracts) related to a particular wallet address on blockchains like Ethereum, Binance Smart Chain, etc.
Practical examples include:
- Monitoring internal contract interactions for a given wallet.
- Auditing transaction flows inside decentralized applications.
- Tracking token movements or contract calls that do not appear as external transactions.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to query (e.g., Ethereum, Binance Smart Chain). |
| network | The specific network environment (e.g., mainnet, testnet) of the chosen blockchain. |
| address | The wallet address for which to list internal transactions. |
| context | Optional context string to correlate responses with requests (useful for tracking). |
| limit | Optional number to limit the number of returned internal transactions. |
| sortingOrder | Optional order to sort results, e.g., ascending or descending. |
| startingAfter | Optional cursor for pagination to start listing after a specific transaction ID. |
Output
The node outputs a JSON array where each item represents an internal transaction related to the specified address. Each JSON object contains details such as transaction identifiers, involved addresses, amounts, timestamps, and other metadata provided by the Crypto APIs service.
If binary data were returned (not indicated here), it would typically represent raw transaction data or logs, but this operation focuses on JSON transaction records.
Dependencies
- Requires an active connection to the Crypto APIs REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- No additional external dependencies beyond standard n8n environment and Crypto APIs access.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication errors.
- Incorrect blockchain or network parameters may result in no data or errors.
- Providing an invalid wallet address format can lead to request failures.
- Pagination parameters (
limit,startingAfter) must be used carefully to avoid empty results.
Error messages:
"Operation <operationName> not found": Indicates the requested operation is not recognized; ensure correct operation selection.- API errors from Crypto APIs (e.g., rate limits, invalid parameters) will be passed through; check API documentation for resolution.
- Network connectivity issues will cause request failures; verify internet access and API endpoint availability.