To build a wallet’s asset history, first decide what counts as a transfer. In an article published on November 11, 2026, at 21:42 (UTC+8), the author uses Quicknode Explorer API’s qn_getAssetTransfers method to explain why a wallet’s transfer history is not the same as its transaction history.
Native-coin payments appear in transactions, while ERC-20, ERC-721 and ERC-1155 transfers appear in event logs. ETH transferred during a contract call may appear only in an execution trace—a record of what happened inside the call. Looking only at transactions and logs can therefore leave transfers out of the history.
For each returned record, the article describes a transferId, direction, amount as both a raw integer and a human-readable decimal, transaction hash, and block time. It recommends using transferId rather than the transaction hash as the record’s primary key: one swap can produce multiple transfers.
The article 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 query can include up to 25 addresses. Its TypeScript example exports the full history as newline-delimited JSON (NDJSON) using cursor-based pagination. The cursor must be reused with exactly the query parameters that produced it, or the API returns Invalid params. When token metadata is missing, decimals and value are null.

