debug_getModifiedAccountsByNumber
Debug & Trace | Arbitrum
debug_getModifiedAccountsByNumber | Arbitrum
Arbitrum API method that retrieves a list of accounts that were modified in a specific block or between two blocks, identified by block number.
POST
debug_getModifiedAccountsByNumber
Arbitrum API method that retrieves a list of accounts that were modified in a specific block or between two blocks, identified by block number. This method compares the state tries between the specified blocks to find all accounts with changed state.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
startNum— the block number (as a decimal integer) for which to retrieve modified accounts. When only this parameter is provided, the method returns accounts modified in this single block (compared to its parent).endNum— (optional) the end block number (as a decimal integer). When provided, the method returns accounts modified betweenstartNumandendNum.
Response
result— an array of account addresses that were modified in the specified block or range.
debug_getModifiedAccountsByNumber code examples
Use case
Thedebug_getModifiedAccountsByNumber method is useful for monitoring state changes over a range of blocks. Developers can use it to build state diff tools, track which accounts are affected by a series of transactions, or perform forensic analysis on state changes across a block range. Unlike debug_getModifiedAccountsByHash, this method accepts block numbers, making it more convenient for iterating over sequential blocks.Body
application/json
Last modified on May 18, 2026