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

# ots_getBlockDetails | Hyperliquid EVM

> The ots_getBlockDetails JSON-RPC method retrieves expanded block details by block number on the Hyperliquid EVM blockchain. On Hyperliquid EVM.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `ots_getBlockDetails` JSON-RPC method retrieves expanded block details by block number on the Hyperliquid EVM blockchain. This Otterscan-specific method provides a tailored response for block detail pages in block explorers, including calculated total fees and other aggregated information.

## Parameters

1. **block number** (integer, required): The block number to retrieve details for

## Response

The method returns an enhanced block object with additional calculated fields.

### Response structure

* `block` — standard block object with all transactions
  * `number` — the block number
  * `hash` — the block hash
  * `parentHash` — the parent block hash
  * `timestamp` — Unix timestamp of the block
  * `gasLimit` — maximum gas allowed in the block
  * `gasUsed` — total gas used by all transactions
  * `miner` — address that mined/validated the block
  * `baseFeePerGas` — base fee per gas (post-EIP-1559)
  * `transactions` — array of transaction objects
  * `transactionCount` — number of transactions in the block
* `issuance` — block reward issuance information
  * `blockReward` — reward for mining the block
  * `uncleReward` — rewards for uncle blocks
  * `issuance` — total new ETH issued
* `totalFees` — total transaction fees collected in the block (in wei)

## Usage example

`ots_getBlockDetails` is an Otterscan-namespace method, so the mainstream EVM libraries have no typed helper for it — call it through each client's raw JSON-RPC request method, as shown below.

<CodeGroup>
  ```shell Shell theme={"system"}
  curl -X POST https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
    -H "Content-Type: application/json" \
    -d '{
      "jsonrpc": "2.0",
      "method": "ots_getBlockDetails",
      "params": [1000],
      "id": 1
    }'
  ```

  ```python web3.py theme={"system"}
  from web3 import Web3

  w3 = Web3(Web3.HTTPProvider("YOUR_CHAINSTACK_ENDPOINT"))

  response = w3.provider.make_request("ots_getBlockDetails", [1000])
  print(response["result"])
  ```

  ```javascript ethers.js theme={"system"}
  import { JsonRpcProvider } from "ethers";

  const provider = new JsonRpcProvider("YOUR_CHAINSTACK_ENDPOINT");

  const result = await provider.send("ots_getBlockDetails", [1000]);
  console.log(result);
  ```

  ```typescript viem theme={"system"}
  import { createPublicClient, http } from "viem";

  const client = createPublicClient({
    transport: http("YOUR_CHAINSTACK_ENDPOINT"),
  });

  const result = await client.request({
    method: "ots_getBlockDetails",
    params: [1000],
  });
  console.log(result);
  ```
</CodeGroup>

<Note>
  **Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

### Example response

```json theme={"system"}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "block": {
      "number": "0x3e8",
      "hash": "0xe8399bf41516f5ca663c79bc30db02b4989385c2f3a96f42958dea5753cbf4a9",
      "parentHash": "0x7c8f6a0e4d3b2a1c9e5f8b7d4a6c3e9f2b8d5a7c1e4f9b3a6d8c2e5f7a9b4c6d",
      "timestamp": "0x6734e8d0",
      "gasLimit": "0x1c9c380",
      "gasUsed": "0x5208",
      "miner": "0x0000000000000000000000000000000000000000",
      "baseFeePerGas": "0x7",
      "transactions": [
        {
          "hash": "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381",
          "from": "0x1234567890abcdef1234567890abcdef12345678",
          "to": "0x5555555555555555555555555555555555555555",
          "value": "0xde0b6b3a7640000",
          "gas": "0x5208",
          "gasPrice": "0x3b9aca00"
        }
      ],
      "transactionCount": 1
    },
    "issuance": {
      "blockReward": "0x0",
      "uncleReward": "0x0",
      "issuance": "0x0"
    },
    "totalFees": "0x1236efcbcbb340"
  }
}
```

## Use cases

The `ots_getBlockDetails` method is essential for:

* **Block explorers**: Display comprehensive block information pages
* **Fee analysis**: Calculate and display total fees collected in blocks
* **Mining analytics**: Track block rewards and issuance
* **Network monitoring**: Monitor block production and transaction throughput
* **Historical analysis**: Study block characteristics over time
* **Gas price tracking**: Analyze gas usage and pricing trends
* **MEV analysis**: Calculate MEV extraction by comparing fees
* **Validator performance**: Track validator rewards and efficiency
* **Chain analytics**: Generate statistics about block utilization
* **Research tools**: Analyze blockchain economics and fee markets

This method provides all the information needed to create detailed block explorer pages, eliminating the need for multiple API calls to gather block data.


## OpenAPI

````yaml openapi/hyperliquid_node_api/hyperevm/evm_ots_get_block_details.json post /evm
openapi: 3.0.0
info:
  title: Hyperliquid EVM API - ots_getBlockDetails
  version: 1.0.0
servers:
  - url: >-
      https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
  /evm:
    post:
      summary: ots_getBlockDetails
      description: >-
        Get detailed block information by block number on Hyperliquid EVM.
        Includes transaction summaries and block metadata.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - jsonrpc
                - method
                - params
                - id
              properties:
                jsonrpc:
                  type: string
                  enum:
                    - '2.0'
                  default: '2.0'
                  description: JSON-RPC version
                method:
                  type: string
                  enum:
                    - ots_getBlockDetails
                  default: ots_getBlockDetails
                  description: The RPC method name
                params:
                  type: array
                  description: 'Parameters: [block number]'
                  default:
                    - 1000
                id:
                  type: integer
                  default: 1
                  description: Request identifier
            example:
              jsonrpc: '2.0'
              method: ots_getBlockDetails
              params:
                - 1000
              id: 1
      responses:
        '200':
          description: Successful response with detailed block information
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                    description: JSON-RPC version
                  id:
                    type: integer
                    description: Request identifier
                  result:
                    type: object
                    description: Detailed block information
              example:
                jsonrpc: '2.0'
                id: 1
                result:
                  block:
                    number: '0x3e8'
                    hash: >-
                      0xe8399bf41516f5ca663c79bc30db02b4989385c2f3a96f42958dea5753cbf4a9
                  transactions: []

````