A wallet’s asset history needs more than a list of transactions. A guide published on November 11, 2026 describes using Quicknode Explorer API’s qn_getAssetTransfers method to build a transfer-data layer for EVM wallets.
The distinction is where each movement 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 appears only in the execution trace. Reading transactions and logs without traces can therefore miss transfers.
For each returned record, the guide identifies a transferId, direction, amount as both a raw integer and a human-readable decimal value, transaction hash, and block time. Use transferId rather than the transaction hash as the record key: one swap can produce multiple transfers.
The method supports server-side filtering by direction, transfer type (native, internal, fungible or non-fungible), and block-height range. The guide also covers filtering zero-value poisoning transfers and querying up to 25 addresses per request.
For a complete export, it describes a TypeScript script that writes cursor-paginated results as NDJSON. Each cursor must be reused with exactly the query parameters that produced it; otherwise, the API returns Invalid params. When token metadata is missing, decimals and value can be null and need to be handled as missing values, not assumed to be zero.
