> ## 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.

# debug_storageRangeAt | Base

> The debug_storageRangeAt RPC method retrieves storage entries from a contract at a specific block. Available on Base via Chainstack.

<Warning>
  **Use eth\_getStorageAt instead**

  Chainstack BASE nodes are on Reth. Reth does not support the `debug_storageRangeAt` method. See [Using eth\_getStorageAt instead of debug\_storageRangeAt on Reth](/docs/using-eth_getstorageat-instead-of-debug_storagerangeat-on-reth).
</Warning>

The `debug_storageRangeAt` RPC method retrieves storage entries from a contract at a specific block. This method is useful for developers and analysts who need to inspect the state of a contract's storage at a particular point in time.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Request

To use `debug_storageRangeAt`, send a POST request with a JSON RPC call in the body.

## Parameters

* **Block Hash** (`string`): The hash of the block.
* **Transaction Index** (`integer`): The index of the transaction in the block.
* **Contract Address** (`string`): The address of the contract.
* **Storage Key** (`string`): The starting point of the storage to inspect.
* **Max Results** (`integer`): The maximum number of storage entries to return.

## Response

The response includes storage entries within the specified range and a flag indicating if the storage snapshot is complete.

* **storage** (`object`): A map of storage entries.
* **complete** (`boolean`): Indicates whether the snapshot of storage is complete.

## Use case

The `debug_storageRangeAt` method is essential for:

* Developers debugging smart contracts by inspecting storage states at specific blocks.
* Analysts conducting forensic analysis of contract interactions.
* Tools and services that provide insights into contract state changes over time.


## OpenAPI

````yaml /openapi/base_node_api/debug_storageRangeAt.json POST /2fc1de7f08c0465f6a28e3c355e0cb14
openapi: 3.0.0
info:
  title: debug_storageRangeAt example
  version: 1.0.0
  description: >-
    This API example demonstrates how to use the debug_storageRangeAt method to
    retrieve storage at a specific  point in a block.
servers:
  - url: https://base-mainnet.core.chainstack.com
security: []
paths:
  /2fc1de7f08c0465f6a28e3c355e0cb14:
    post:
      tags:
        - Debug Operations
      summary: debug_storageRangeAt
      operationId: getStorageRangeAt
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - jsonrpc
                - method
                - id
                - params
              properties:
                jsonrpc:
                  type: string
                  default: '2.0'
                method:
                  type: string
                  default: debug_storageRangeAt
                id:
                  type: integer
                  default: 1
                params:
                  type: array
                  items:
                    oneOf:
                      - type: string
                      - type: integer
                  default:
                    - >-
                      0xc40b7058b5b80e565dfb986fe852c047733291291c8de1be8888ae64b5457bbd
                    - 25
                    - '0x833589fcd6edb6e08f4c7c32d4f71b54bda02913'
                    - '0x00000000000000000000000000000000'
                    - 2
      responses:
        '200':
          description: Storage data for the specified range
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: object
                    properties:
                      storage:
                        type: object
                        additionalProperties: true
                      complete:
                        type: boolean
                    description: >-
                      The storage entries and a flag indicating if the storage
                      is complete.

````