eth_getUncleCountByBlockHash
Returns the number of uncles included in a block.
Ethereum specification · All supported methods
Parameters
Parameters are positional, in the order below.
| Parameter | Type | Required | Description |
|---|---|---|---|
block | Block hash | Yes | Block containing the included uncle. |
Return value
The count as a hexadecimal quantity, or null if the block is not found.
Example
Replace <gateway-url> with your gateway base URL and <service-url> with the chain’s service path, such as service/ethereum.
sh
curl -X POST "<gateway-url>/<service-url>" \
-H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_getUncleCountByBlockHash","params":["0x1111111111111111111111111111111111111111111111111111111111111111"]}'Illustrative response; values depend on the selected network and request:
json
{
"jsonrpc": "2.0",
"id": 1,
"result": "0x0"
}Direct behavior
Requests for older chain data are automatically routed to providers with full chain history. This covers blocks, transactions, receipts, and logs independently of historical account state.
The gateway uses the block’s age when known. If the age is unknown, it starts with a full-history provider. A missing result from a provider without the required history is not accepted as proof that the data does not exist.
For providers
Support the required recent chain-history service. Advertise full chain history only when all included method families and lookup indexes work back to genesis.
Checks use known blocks containing uncles as well as empty uncle lists. Pruned data cannot be returned as a legitimate zero or null result.
See provider qualification for checks and continued eligibility.