Docs

trace_callMany - Base RPC Method

Trace multiple calls in sequence on Base. Requires archive node for consumer dApps, SocialFi, NFT marketplaces, and merchant payment integrations.

Traces multiple calls in sequence on Base, 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 Base
  • Historical state comparison - Compare how the same call would execute at different points in Base chain history
  • Multi-step simulation - Simulate a sequence of dependent calls where each step builds on the previous one for consumer dApps, SocialFi, NFT marketplaces, and merchant payment integrations
  • 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

trace_call

Trace a call without creating a transaction on Base. Requires archive node for consumer dApps, SocialFi, NFT marketplaces, and merchant payment integrations.

trace_filter

Filter traces by address and block range on Base. Requires archive node for consumer dApps, SocialFi, NFT marketplaces, and merchant payment integrations.

On this page

When to Use This MethodBest PracticesCode ExamplesRelated Methods