A wallet’s transfer history is not the same as its transaction history. In a guide published on November 11, 2026, Quicknode’s Explorer API method qn_getAssetTransfers was used to build an asset-flow data layer for EVM wallets. The key question is where each type of movement appears in the record.
A native-coin payment appears in the transaction itself. ERC-20, ERC-721 and ERC-1155 transfers appear in event logs. ETH transferred during a contract call appears only in an execution trace. Reading transactions and logs without traces can therefore leave gaps in an asset history.
The guide’s transfer records include a transferId, direction, an amount as both a raw integer and a human-readable decimal value, a transaction hash, and block time. An application should use transferId as the record key rather than the transaction hash: one swap can produce multiple transfers within a single transaction.
qn_getAssetTransfers also supports server-side filtering by direction, transfer type (native, internal, fungible or non-fungible), and block-height range. The guide covers filtering zero-value poisoning transfers and querying up to 25 addresses in one request.
For a full-history export, the guide provides a TypeScript example that paginates with a cursor and writes NDJSON. Each subsequent request must keep exactly the same query parameters that produced the cursor; otherwise, the API returns Invalid params. When token metadata is missing, decimals and value can be null, which an export or downstream reader must handle rather than treating as a measured zero.