A guide published on November 11, 2026, describes using Quicknode Explorer API’s qn_getAssetTransfers method as the data layer for an EVM wallet’s asset history. The key distinction is transfer history versus transaction history: a single transaction, such as a swap, can produce multiple transfers.
To build a more complete history, account for where each kind of transfer appears. Native-coin payments are recorded in transactions; ERC-20, ERC-721 and ERC-1155 transfers appear in event logs; and ETH transferred during a contract call may appear only in an execution trace. Looking only at transactions and logs can therefore miss transfers.
For each returned transfer, retain its transferId as the record key rather than using the transaction hash: several transfers can share one transaction. The described records also include direction, a raw integer amount and human-readable decimal amount, transaction hash, and block time.
The guide describes server-side filters for direction, transfer type (native, internal, fungible or non-fungible), block-height range and zero-value poisoning transfers. A single query can cover up to 25 addresses. For a full-history export, its TypeScript example uses cursor pagination to write NDJSON. Keep the query parameters identical when reusing a cursor; changing them produces an Invalid params error. If token metadata is missing, handle decimals and value as null rather than assuming a converted amount is available.

