Building an EVM Wallet Transfer History with Quicknode Explorer API

To build a wallet’s asset history, first decide what counts as a transfer. As described in a November 11, 2026 guide to Quicknode Explorer API’s qn_getAssetTransfers method, transfer history is not the same as transaction history: native-coin payments appear in transactions, ERC-20/721/1155 transfers appear in event logs, and ETH moved during a contract call may appear only in an execution trace. Reading transactions and logs alone can therefore miss transfers.

The method returns records with a transferId, direction, amount as both a raw integer and a human-readable decimal, transaction hash, and block time. Use transferId rather than the transaction hash as a record’s primary key: one swap can produce multiple transfers.

The guide also covers server-side filters for direction, transfer type (native, internal, fungible or non-fungible), block-height range and zero-value poisoning transfers. A single request can query at most 25 addresses.

For a complete export, the guide describes a TypeScript script that paginates with a cursor and writes NDJSON (newline-delimited JSON). Each subsequent request must keep exactly the same query parameters that produced its cursor; otherwise the API returns Invalid params. If token metadata is unavailable, decimals and value can be null, so an exporter must account for missing values.