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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.chainstack.com/feedback

```json
{
  "path": "/reference/hyperliquid-evm-eth-get-uncle-count-by-block-number",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# eth_getUncleCountByBlockNumber | Hyperliquid EVM

> Returns the number of uncle blocks for a given block number.

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

Returns the number of uncle blocks for a given block number. Use this method to get the count of uncle (ommer) blocks associated with a block identified by its number.

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

## Parameters

* `blockNumber` (string, required) — Block number in hex format, or one of the special tags: "earliest", "latest", "pending", or "finalized"

## Returns

Returns the number of uncle blocks as a hex-encoded integer, or `null` if the block is not found.

<Note>
  On Hyperliquid, uncle blocks are not part of the consensus mechanism. This method is included for Ethereum compatibility but will typically return "0x0" as Hyperliquid doesn't produce uncle blocks.
</Note>

## Use cases

* **Ethereum compatibility** — Maintain compatibility with Ethereum RPC interfaces
* **Network monitoring** — Track uncle block production across different block heights
* **Performance analysis** — Analyze network efficiency and block production patterns
* **Compatibility testing** — Verify application behavior when migrating from Ethereum
* **Protocol comparison** — Compare consensus mechanisms between networks
* **API completeness** — Implement full Ethereum RPC compatibility


## OpenAPI

````yaml /openapi/hyperliquid_node_api/evm_eth_get_uncle_count_by_block_number.json post /evm
openapi: 3.0.0
info:
  title: Hyperliquid EVM API - eth_getUncleCountByBlockNumber
  version: 1.0.0
servers:
  - url: >-
      https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
  /evm:
    post:
      summary: eth_getUncleCountByBlockNumber
      description: Returns the number of uncle blocks for a given block number.
      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:
                    - eth_getUncleCountByBlockNumber
                  default: eth_getUncleCountByBlockNumber
                  description: The RPC method name
                params:
                  type: array
                  description: 'Parameters: [blockNumber]'
                  default:
                    - latest
                id:
                  type: integer
                  default: 1
                  description: Request identifier
            example:
              jsonrpc: '2.0'
              method: eth_getUncleCountByBlockNumber
              params:
                - latest
              id: 1
      responses:
        '200':
          description: Successful response with uncle count
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                    description: JSON-RPC version
                  id:
                    type: integer
                    description: Request identifier
                  result:
                    type: string
                    description: >-
                      Number of uncle blocks as hex-encoded integer, or null if
                      block not found
              example:
                jsonrpc: '2.0'
                id: 1
                result: '0x0'

````