trace_callMany - Tempo RPC Method
Trace multiple calls in sequence on Tempo. Requires archive node for merchant settlement, treasury operations, payout automation, and stablecoin-native financial applications.
Tempo RPC endpoint: endpoint URLs, plans and pricing.
Traces multiple calls in sequence on Tempo, where each call can depend on the state changes of the previous one.
Archive Node Required
This method requires an archive node. It is not available on full nodes.
When to Use This Method
- Trace multiple calls across different blocks - Execute calls at different historical block heights for cross-block state analysis on Tempo
- Historical state comparison - Compare how the same call would execute at different points in Tempo chain history
- Multi-step simulation - Simulate a sequence of dependent calls where each step builds on the previous one for merchant settlement, treasury operations, payout automation, and stablecoin-native financial applications
- Batch operation tracing - Preview multiple contract interactions in a single RPC request
Best Practices
- Each call specifies its own block number for cross-block analysis
- Useful for comparing state across time without multiple requests
- More efficient than separate trace_call requests for multi-step workflows
- Requires archive node access for historical block state
Response Body
Code Examples
Related Methods
trace_call- Trace a single calleth_call- Execute call without trace
trace_call
Simulate a call on Tempo with Parity-style trace_call. Choose trace, vmTrace or stateDiff output for a block, without sending a transaction.
trace_filter
Filter traces by address and block range on Tempo. Requires archive node for merchant settlement, treasury operations, payout automation, and stablecoin-native financial applications.