debug_dumpBlock
Debug & Trace | Arbitrum
debug_dumpBlock | Arbitrum
Arbitrum API method that retrieves the state of all accounts at a given block number. Available on Arbitrum via Chainstack JSON-RPC nodes.
POST
debug_dumpBlock
Arbitrum API method that retrieves the state of all accounts at a given block number. This method returns a dump of the state trie, including account balances, nonces, code hashes, and storage. It is primarily used for debugging and state inspection.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
quantity— the block number in hex format or block tag (latest,earliest,pending,safe,finalized).
Response
result— an object containing the state dump:root— the state root hash of the block.accounts— a map of account addresses to account data:balance— the account balance in Wei.nonce— the account nonce.root— the storage root hash.codeHash— the hash of the account’s contract code.code— the contract bytecode.storage— the account’s storage slots.address— the account address.
debug_dumpBlock code examples
Use case
Thedebug_dumpBlock method is useful for inspecting the state of all accounts at a specific block. Developers can use it to verify account states during debugging, compare state snapshots between blocks, or build tools that analyze the distribution of contract deployments and account balances at a point in time.Body
application/json
Last modified on May 18, 2026