debug_intermediateRoots
Debug & Trace | Arbitrum
debug_intermediateRoots | Arbitrum
Arbitrum API method that computes the intermediate state roots for a given block by re-executing all transactions. Arbitrum via Chainstack.
POST
debug_intermediateRoots
Arbitrum API method that computes the intermediate state roots for a given block by re-executing all transactions. For each transaction in the block, it returns the state root after that transaction was applied. This provides a detailed view of how the state trie evolves within a single block.Documentation Index
Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
Use this file to discover all available pages before exploring further.
Learn how to deploy a node with the debug and trace API methods enabled.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
hash— the hash of the block to compute intermediate roots for.object— (optional) tracing configuration:timeout— the timeout for the computation. Defaults to5s. See Go time format for accepted values.reexec— the number of blocks to re-execute to reconstruct historical state. Defaults to 128.
Response
result— an array of state root hashes (as hex strings), one per transaction in the block. Each root represents the state after the corresponding transaction was executed.
debug_intermediateRoots code examples
Use case
Thedebug_intermediateRoots method is useful for verifying state transitions within a block. By computing the intermediate state root after each transaction, developers can identify exactly which transaction caused a state change and verify the correctness of state transitions. This is particularly valuable for building state verification tools and debugging state-related issues in smart contracts.Body
application/json
Last modified on May 18, 2026