Block ID

Overview

Meaning and scope

A block ID is the protocol-specific identifier used to reference a particular blockchain block, commonly a hash of its header or another cryptographic commitment. It distinguishes blocks that may share the same block number or height during a fork. The identifier should always be stored with the network and, where relevant, the chain or shard.

Mechanism and operation

Most blockchains derive a block identifier from cryptographically encoded block data. In Bitcoin, the block header hash identifies the block and binds fields such as the previous block hash and Merkle root. Ethereum APIs expose a block hash together with the parent hash, block number, transaction root, state root, and receipt root. Other protocols can use signed headers or composite identifiers, so the exact calculation is network-specific. Applications that store only “transaction confirmed at block 100” may fail to detect the replacement. Storing the actual identifier allows software to verify that the same block remains in the Canonical Chain.

Practical payment example

A support analyst records the canonical block identifier, not only a displayed height, when diagnosing a short reorganization.

Operational checks

An identifier can be valid for a noncanonical, stale, or maliciously supplied block. Light clients and payment systems must verify parent links, consensus evidence, and the node’s current chain view. The hash also does not make the complete block data available. A service can provide a genuine block ID while omitting transactions or returning an incomplete interpretation.

Distinctions and limits

Two Competing Chain branches can contain different blocks at the same height, and a reorganization can replace the block previously associated with a number. Verification requires the relevant header, proofs, or full data under the protocol’s rules.

Related reading

Related definitions: Competing Chain, Canonical Chain.