Find internal calls and contract creations
portal_evm_query_tracesQuery raw EVM traces: internal calls, contract creations, self-destructs, and block rewards, filtered by caller, callee, method, deployer, or one transaction, with the parent transaction hash on every row.
COMMON USER ASKS:
Internal calls of one transaction
Recent internal calls into a contract
Contracts deployed by an address
FIRST CHOICE FOR:
what a transaction called internally, including value moved by internal calls
contracts deployed by an address, or the internal call tree behind an incident
WHEN TO USE:
You need the internal calls of a transaction: which contracts it called, with what selector and value, and which calls failed.
You want contracts created by a deployer or the creation trace of a contract.
You are tracing an exploit or incident below the top-level transaction and log surface.
You want internal ETH transfers between contracts that emit no event.
DON'T USE:
You only need top-level transactions or event logs; those tools are cheaper.
You need storage changes; state diffs are not exposed by this tool.
EXAMPLES:
Internal calls of one transaction: {"network":"ethereum-mainnet","from_block":12244145,"to_block":12244145,"transaction_hash":"0x851bad0415758075a1eb86776749c829b866d43179c57c3e4a4b9359a0358231","limit":25}
Recent internal calls into a contract: {"network":"base-mainnet","timeframe":"10m","type":["call"],"call_to":["0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"],"method":"transfer","limit":20}
Contracts deployed by an address: {"network":"base-mainnet","timeframe":"24h","type":["create"],"create_from":["0x4200000000000000000000000000000000000006"],"limit":10}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | FILTER: trace types. 'create' covers both CREATE and CREATE2; 'reward' only exists on proof-of-work history. | |
| limit | No | Max traces to return (default: 20, max: 25) | |
| cursor | No | Continuation cursor from a previous response | |
| method | No | FILTER (call traces): method alias such as transfer, approve, deposit, or a 4-byte selector. Merges with call_sighash. | |
| call_to | No | FILTER (call traces): called addresses. | |
| network | No | Network name or alias. Optional when continuing with cursor. | |
| to_block | No | Ending block number. Traces are expensive: keep filtered windows under 5,000 blocks. | |
| call_from | No | FILTER (call traces): calling addresses, contracts or wallets. | |
| timeframe | No | Time range (e.g., '10m', '1h'). Alternative to from_block/to_block. Keep it short for traces. | |
| from_block | No | Starting block number (use this OR timeframe) | |
| scan_order | No | Which side of the block window to scan first. Use earliest for first-occurrence questions. | latest |
| create_from | No | FILTER (create traces): deployer addresses. | |
| call_sighash | No | FILTER (call traces): 4-byte selectors such as 0xa9059cbb. | |
| field_preset | No | Field preset: 'minimal' (type, from, to), 'standard' (value, selector, gas, result address), 'full' (adds call input and output and creation code). | standard |
| to_timestamp | No | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | No | Only query finalized blocks | |
| from_timestamp | No | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| max_scan_blocks | No | Safety cap for bounded scans. Default: 5,000 blocks with filters, 100 without. | |
| response_format | No | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by type, failures, value moved, and top callers. | |
| transaction_hash | No | FILTER: keep only traces of this transaction. Give its block (from_block = to_block) or a window of at most 1,000 blocks; find the block with portal_evm_query_transactions first when unknown. | |
| include_subtraces | No | Also return the child traces of each matching trace | |
| include_transaction | No | Attach the parent transaction (sender, recipient, value, status). The hash is always attached. | |
| create_result_address | No | FILTER (create traces): deployed contract addresses. |
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. |