Block Body

Overview

Meaning and scope

The block body contains the transactions and other consensus-defined payloads associated with a blockchain block, separate from its compact header. The header usually commits cryptographically to body contents through roots or hashes. A node can reject a block if the body is missing, malformed, exceeds limits, contains invalid objects, or does not match those commitments.

Mechanism and operation

A block body contains the transaction data and any other consensus-defined payload separate from the block header. A validator downloads the body, checks transaction syntax and authorization, and applies the transactions according to the protocol rules. In Bitcoin, the transaction list must match the Merkle-root commitment carried by the header; SegWit witness data is accounted for through additional commitments. On Ethereum-like chains, transaction and receipt commitments also let clients validate execution results. Header availability alone is insufficient to execute or fully verify the block. A node can discover a plausible header before it has obtained a complete valid body. Relay protocols may compress the data or reconstruct it from a mempool, but the underlying transactions still need independent validation.

Practical payment example

A chain indexer reads the transactions in a block body and compares their Merkle root with the commitment in the block header.

Operational checks

Confirm that every required transaction or payload is available, validate commitments, apply protocol rules, and retain a canonical block identifier when indexing the result. A block body is the main payload carried by a block after the header. Depending on the blockchain, it may include ordered transactions, attestations, withdrawals, receipts, uncle references, evidence, or other protocol objects needed to execute and validate the state transition. Indexers and payment systems should not treat a header announcement as proof that transaction data has been received and validated. They need the canonical body or trustworthy derived data, transaction position, execution result, and finality status.

Distinctions and limits

The block header summarizes and commits to data; the block body carries the content that must actually be inspected and executed.

Related reading

Related definitions: block, transaction data.