In this track: From send to settlement
What is a chain reorganization?
A node can replace its view of recent unfinalized blocks with another valid branch.
Two draft notebook pages can temporarily compete. When the group chooses one branch, records from the other draft may no longer be in the accepted sequence.
Maya prepares an instruction: send 0.01 pretend ETH to Leo.
A local simulation. Nothing is signed or sent to a network.
A chain head is a current choice
Nodes follow a fork-choice process for the chain head. Delayed information and competing proposals can cause the accepted recent branch to change. A block’s existence somewhere is not proof that it is currently canonical.
Transactions may change context
A transaction from a displaced block might be included later in another block, become pending again in some views, or lose its previous result context. Its block number, receipt association or execution outcome can change.
Finality adds stronger settlement
Ethereum’s checkpoint finality rules give a different security commitment from merely being near the head. Finality depends on protocol assumptions and participation; it is not the same as a website’s arbitrary confirmation badge.
Interfaces need careful labels
Applications that respond to recent logs should handle the possibility that the containing block is no longer canonical. Learn receipts and events to understand which records are tied to a specific block hash.
Can a recent unfinalized receipt’s block context change after a reorganization?
The accepted branch can change while the original encoded transaction remains the same.
Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.