eth_callMany

Executes one or more bundles of eth_call-style transactions against an ephemeral state, without committing state to the chain. Transactions within each bundle are executed sequentially: state changes from earlier transactions in the bundle are visible to later ones. You can optionally override selected block header fields per bundle.

Path parameters

apiKeystringRequiredDefaults to docs-demo

Request

This endpoint expects an object.
Bundleslist of objectsRequired

A list of bundles to execute. Each bundle specifies a list of transactions (executed in order) and may include a per-bundle block header override.

Simulation contextobjectRequired

The base context for the simulation. If a bundle supplies blockOverride, it takes precedence for that bundle. transactionIndex is 0-based within the referenced block.

State overridesmap from strings to objectsOptional

Optional per-account state overrides applied during execution, identical in shape to the eth_call state override parameter.

TimeoutintegerOptional>=1

Maximum running time for the simulations in milliseconds. If omitted, the node’s default is used (commonly 5000).

Response

A list with one entry per bundle. Each bundle entry is an array with one result per transaction in that bundle, in execution order. Each transaction result is either a successful return value (ABI-encoded bytes), or an error describing the revert/failure.

object
OR
object