Pioneer Web

Mapping an EVM Wallet’s Asset Transfers with Quicknode Explorer API

As described in a guide published on November 11, 2026, Quicknode Explorer API’s qn_getAssetTransfers method can serve as the data layer for an EVM wallet’s asset-transfer history. The key distinction is between transactions and transfers: one transaction can produce multiple asset movements, while some movements are not visible in the transaction record alone.

Native-coin payments appear in transactions. ERC-20, ERC-721 and ERC-1155 transfers appear in event logs. ETH transferred during a contract call appears only in the execution trace. A history built from transactions and logs without traces can therefore miss movements.

For each transfer, the guide describes a transferId, direction, amount as both a raw integer and a human-readable decimal value, transaction hash, and block time. It recommends using transferId rather than the transaction hash as the record’s primary key: a swap can generate several transfers under one transaction hash.

The method supports server-side filters for direction, transfer type (native, internal, fungible or non-fungible), block-height range and zero-value transfers. It can query up to 25 addresses in one request. The zero-value filter is useful when reviewing transfers associated with address-poisoning attempts, but it should not be treated as a complete fraud filter.

For a full-history export, the guide uses a TypeScript script to paginate with a cursor and write NDJSON. Each subsequent request must keep exactly the same query parameters that produced its cursor; changing them results in an Invalid params error. Consumers also need to handle missing token metadata: decimals and value can be null.