trace_callMany - Ink RPC Method

Traces multiple calls in sequence on Ink, where each call can depend on the state changes of the previous one.

When to Use This Method

• Trace multiple calls across different blocks - Execute calls at different historical block heights for cross-block state analysis on Ink
• Historical state comparison - Compare how the same call would execute at different points in Ink chain history
• Multi-step simulation - Simulate a sequence of dependent calls where each step builds on the previous one for low-fee DeFi applications, cross-chain liquidity, and EVM-compatible smart contracts
• 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

Response

Code Examples

Related Methods

• trace_call - Trace a single call
• eth_call - Execute call without trace