Use Case
Call traces help you:- Analyze DEX trades with multiple hops
- Track value flows through proxy contracts
- Monitor internal contract calls
- Debug complex contract interactions
Code Example
Try it yourself with the interactive query interface below:
Key Parameters
| Parameter | Description |
|---|---|
type | Trace type: call (contract calls) or create (contract deployments) |
callFrom | Caller address |
callTo | Callee address |
callValue | ETH value transferred in the call |
callInput | Call input data |
callResultOutput | Call output data |
callResultGasUsed | Gas used by the call |
error | Error message if trace failed |
Portal supports two trace types:
call for regular contract calls and create for contract deployments. Other EVM trace types like staticcall, delegatecall, and callcode are normalized to call type.Expected Output
Filter by Specific Contract
Track all calls to or from a specific contract:Traces include both successful and failed calls. Check the
error field to filter failed traces.Analyze Value Flows
Track ETH transfers through internal calls:Performance Tips
- Filter by type: Specify trace types to reduce data volume
- Use callTo/callFrom: Filter by specific contracts
- Request minimal fields: Omit
inputandoutputif not needed - Post-filter errors: Filter failed traces in your code if needed

