eth_getUncleByBlockNumberAndIndex

The eth_getUncleByBlockNumberAndIndex method returns information about an uncle (ommer) block by a block number and uncle index position.

Use Cases

Analyzing blockchain network health
Verifying uncle rewards distribution
Researching mining/validation competition
Studying blockchain throughput and latency
Understanding network security through uncle rate
Historical blockchain research
Block confirmation verification
Network congestion analysis

Method Details

Returns information about the uncle (ommer) block by the block number and uncle index position.

Block Number Parameter Options

The blockNumber parameter accepts:

Hex string of a block number
"earliest" for the genesis block
"latest" for the most recently mined block
"pending" for the pending state/transactions
"safe" for the most recent block that's safe from reorgs
"finalized" for the most recent finalized block

Response Example

1{
2	"jsonrpc": "2.0",
3	"id": 1,
4	"result": {
5		"difficulty": "0x57f17a09378",
6		"extraData": "0x476574682f76312e302e302f6c696e75782f676f312e342e32",
7		"gasLimit": "0x1388",
8		"gasUsed": "0x0",
9		"hash": "0x932bdf904546a2287a2c9b2ede37925f698a7657484b172d4e5184f80bdd464d",
10		"logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
11		"miner": "0xbb7b8287f3f0a933474a79eae42cbca977791171",
12		"mixHash": "0x4500aa4ee2b3044a155252e35273770edeb2ab6f8cb19ca8e732771484462169",
13		"nonce": "0x24732773618271bc",
14		"number": "0x299",
15		"parentHash": "0xa779859b1ee558258b7008bbabff272280136c5dd3eb3ea3bfa8f6ae03bf91e5",
16		"receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
17		"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
18		"size": "0x21d",
19		"stateRoot": "0x2604fbf5183f5360da249b51f1b9f1e0f315d2ff3ffa1a4143ff221ad9ca1fec",
20		"timestamp": "0x55ba4827",
21		"totalDifficulty": null,
22		"transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
23		"uncles": []
24	}
25}

Understanding Uncle Blocks

Uncle blocks (also called ommers) are valid blocks that were mined but not included in the main blockchain. This happens when two miners find a valid block at nearly the same time, but only one can be accepted into the main chain.

Why Uncle Blocks Matter

Network Security: A high uncle rate may indicate network latency or high mining competition
Rewards: Miners of uncle blocks receive partial rewards (2/32 of block reward pre-EIP-1559)
Block Inclusion: Uncles are referenced in regular blocks (up to 2 per block)
Chain Confirmation: Uncles contribute to blockchain security despite not being in the main chain

Differences Between eth_getUncleByBlockNumberAndIndex and eth_getUncleByBlockHashAndIndex

Both methods retrieve the same uncle block data, but they use different reference methods:

eth_getUncleByBlockNumberAndIndex - Uses the block number (or named tag like "latest") to identify the block containing the uncle
eth_getUncleByBlockHashAndIndex - Uses the block hash to identify the block containing the uncle

The number parameter is often more convenient as it allows using block tags like "latest" and is easier to work with sequentially, while hash-based lookups provide absolute reference certainty.

Historical Significance

Uncle rates in Ethereum have historically been important metrics:

Early Ethereum had uncle rates around 7-10%
Network upgrades like Byzantium and Constantinople adjusted uncle rewards
Post-Merge (PoS transition), uncle blocks no longer exist as validators produce blocks in determined slots

Example Usage

1// Get the latest uncle block
2async function getLatestUncle() {
3  // First, find a recent block with uncles
4  let blockNumber = "latest";
5  let uncleCount = 0;
6 
7  while (uncleCount === 0) {
8    // Get the block
9    const block = await provider.send("eth_getBlockByNumber", [blockNumber, false]);
10 
11    // Check uncle count
12    uncleCount = block.uncles.length;
13 
14    // If no uncles, check previous block
15    if (uncleCount === 0) {
16      blockNumber = "0x" + (parseInt(block.number, 16) - 1).toString(16);
17    }
18  }
19 
20  // Once we find a block with uncles, get the first uncle
21  const uncleBlock = await provider.send("eth_getUncleByBlockNumberAndIndex", [
22    blockNumber,
23    "0x0"
24  ]);
25 
26  return uncleBlock;
27}