eth_getUncleCountByBlockNumberHTTP

Returns the uncle count for a block selected by number or tag. On post-merge Ethereum and most non-PoW chains this is typically 0x0.

Chain EthereumTransport HTTPTry-it live

How to use

Pick an API key (or paste one) in the Try it panel.
Fill each parameter (order = params array index).
Send request — live against the gateway; counts toward daily quota.

Parameters

JSON-RPC positional arguments — order matches the array sent in params. Index badges below match array positions.

blockQUANTITY|TAGrequired

Block number or tag.

params array (shape)

eth_getUncleCountByBlockNumber · paramsjson

1[
2  "latest"
3]

Try it

Live request via the gateway — counts toward your account's daily quota. Chain: ethereum

JSON mode

API key

Try-it runs with one of your own keys — sign in or create a free account first.

Parameters

0blockQUANTITY|TAGrequired

Block number or tag.

Example request

eth_getUncleCountByBlockNumber · requestbash

1curl 'https://ethras.org/v1/ethereum/<YOUR_KEY>' \
2  -H 'Content-Type: application/json' \
3  -d '{
4    "id": 1,
5    "jsonrpc": "2.0",
6    "method": "eth_getUncleCountByBlockNumber",
7    "params": [
8      "latest"
9    ]
10  }'

Example response

Illustrative example: long hex values and object fields may be shortened for readability. Available fields depend on the network, client, protocol upgrade and transaction type.

eth_getUncleCountByBlockNumber · responsejson

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "result": "0x0"
5}

Response fields

The result row describes the complete result; other rows describe its object fields or array elements. Indented rows describe nested members. For subscriptions,params.* rows describe later notifications rather than the initial reply.

Field	Type	Description
`result`	`QUANTITY\|null`	Ommer count, zero for Ethereum blocks after the Merge. Historical PoW blocks may have ommers. Null when the block is unavailable; zero and null are distinct.