Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation allows users to list transactions associated with HD Wallets (using extended public keys such as xPub, yPub, zPub) on EVM-compatible blockchains. It fetches transaction data for a given blockchain, network, and extended public key, optionally supporting pagination and derivation context.

Common scenarios include:

  • Monitoring all transactions related to an HD wallet's extended public key on Ethereum or other EVM chains.
  • Auditing wallet activity without exposing private keys.
  • Integrating wallet transaction history into dashboards or analytics tools.

Practical example:

  • A user inputs their Ethereum xPub key and requests the latest 50 transactions on the mainnet to display in a portfolio tracker.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Ethereum, Binance Smart Chain).
extendedPublicKey The HD wallet's extended public key (xPub, yPub, zPub) identifying the wallet addresses.
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to specify additional filtering or usage context.
derivation Optional derivation type; currently supports "account" to specify account-level derivation.
limit Optional number to limit the number of returned transactions (pagination).
offset Optional number to skip a certain number of transactions (pagination offset).

Output

The output is a JSON array where each item represents a transaction related to the specified HD wallet extended public key on the chosen EVM blockchain network. Each transaction object typically includes details such as transaction hash, block number, timestamp, from/to addresses, value transferred, and status.

If binary data were involved (not indicated here), it would represent raw transaction payloads or receipts, but this operation focuses on JSON transaction data.

Dependencies

  • Requires an API key credential for accessing the Crypto APIs REST API service.
  • The node depends on the Crypto APIs service endpoint that provides blockchain data for HD wallets.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Operation not found error: If the specified operation is not recognized, ensure the operation name matches exactly and the node version supports it.
  • Invalid or missing parameters: Required fields like blockchain, extendedPublicKey, and network must be provided; missing these will cause errors.
  • API rate limits or authentication failures: Ensure the API key credential is valid and has sufficient permissions.
  • Empty results: Could indicate no transactions exist for the given extended public key or incorrect network/blockchain selection.
  • Pagination issues: Using limit and offset incorrectly may result in unexpected subsets of data.

Links and References

Discussion