debug_getAccessibleState
Debug & Trace | Arbitrum
debug_getAccessibleState | Arbitrum
Arbitrum API method that finds the first block number in a given range where the state is accessible on disk. Arbitrum via Chainstack.
POST
debug_getAccessibleState
Arbitrum API method that finds the first block number in a given range where the state is accessible on disk. This is useful for determining which historical states are available for querying on the node, as nodes may prune older state data.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
from— the start of the block range to search, as a hex-encoded block number or block tag.to— the end of the block range to search, as a hex-encoded block number or block tag.
Response
result— the block number (as a decimal integer) of the first block in the range where the state is accessible. Returns an error if no accessible state is found in the range.
debug_getAccessibleState code examples
Use case
Thedebug_getAccessibleState method is useful for determining the historical state availability of a node. Before calling state-dependent methods like debug_accountRange or debug_dumpBlock on a specific block, developers can use this method to verify that the node still has the state data for that block. This is particularly relevant for nodes that use state pruning, where older state data may have been removed.Last modified on May 18, 2026