Find token transfers
portal_evm_query_token_transfersQuery token-transfer activity on EVM without needing to remember Transfer event signatures. Best for "did token X move?" and asset-tracing questions.
COMMON USER ASKS:
Recent USDC transfers
First recent USDC transfer
WHEN TO USE:
You want ERC-20 style transfer activity filtered by token, sender, or recipient.
You want the fastest answer to a token movement question like "did USDC move?".
You are tracing suspicious, stolen, bridged, or exploit-related token movement and need sender/recipient/transaction pivots.
You want the easiest raw transfer query on an EVM network.
You need the first matching transfer in a bounded window without typing the Transfer topic hash.
DON'T USE:
You need arbitrary event logs beyond token transfers.
EXAMPLES:
Recent USDC transfers: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"limit":20}
First recent USDC transfer: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"scan_order":"earliest","limit":1}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max transfers | |
| cursor | No | Continuation cursor from a previous response | |
| network | No | Network name or alias. Optional when continuing with cursor. | |
| to_block | No | Ending block number. RECOMMENDED: <10k blocks for fast responses. | |
| timeframe | No | Time range (e.g., '1h', '24h'). Alternative to block numbers. | |
| from_block | No | Starting block number | |
| scan_order | No | Which side of the block window to scan first. Use earliest for first-transfer questions. | latest |
| to_addresses | No | Recipient addresses | |
| to_timestamp | No | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| token_symbols | No | Token symbols to resolve via open token-list data, e.g. ["USDC"]. Merges with token_addresses. | |
| from_addresses | No | Sender addresses | |
| from_timestamp | No | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| token_addresses | No | Token contract addresses | |
| include_token_info | No | Include token metadata (symbol, decimals) inline. Avoids separate token metadata lookups. | |
| max_token_symbol_matches | No | Maximum token-list matches to include per token symbol. Use token_addresses for deterministic single-contract filters. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _ui | No | Chart, table, and follow-up presentation metadata. | |
| _app | No | SQD Explorer identity and host-render state. | |
| _llm | No | Hints to locate the primary evidence. | |
| _meta | No | Network, block range, timing, and row counts. | |
| error | No | Structured failure details. | |
| items | No | Primary rows for list results. | |
| value | No | Primary scalar result. | |
| answer | No | Answer grounded in the returned data. | |
| _notice | No | Limitation or truncation notice. | |
| _server | No | SQD server name, exact version, and git commit. | |
| display | No | Labels for presenting the result. | |
| _notices | No | Limitation or truncation notices. | |
| _summary | No | Human-readable summary. | |
| _coverage | No | Window and result completeness. | |
| _evidence | No | Replayable arguments, digest, row count, and receipt. | |
| _ordering | No | Ordering guarantees. | |
| _execution | No | Bounded execution and scan details. | |
| _freshness | No | Freshness and finality. | |
| next_steps | No | Safe follow-up actions and continuation guidance. | |
| _pagination | No | Pagination state and next_cursor. | |
| investigation | No | Evidence paths, pivots, and limitations. | |
| pipes_handoff | No | SQD Pipes guidance for custom data needs. | |
| _tool_contract | No | Tool identity, intent, and chain families. |