Awarded once after a correct answer.
Track a transaction through distinct states
Useful first : Hashes, keys and signatures · Consensus and finality
Reading path · 3 / 41 · Intermediate
A wallet builds a transaction for a selected network, destination and fee.
The essentials
A wallet builds a transaction for a selected network, destination and fee. After approval, it signs and sends the transaction to a node, often through an RPC service. Block producers choose and order pending transactions; other nodes verify the result.
How it works
Ordering can change economic outcomes. An exchange may receive a different price depending on earlier trades. Maximal extractable value, or MEV, includes value obtained through inclusion, exclusion and ordering, including arbitrage and sandwich attacks. An expected quote is therefore not a guaranteed execution price.
What to watch
A smart contract transaction can revert while still paying for computation. Atomic execution applies its changes together or rolls them back, but does not automatically cover another blockchain or a bank payment. A reconciliation process should track signing, broadcast, inclusion, finality and the receiving system’s ledger entry separately.
Understand the details
A wallet prepares a request, obtains a signature and broadcasts it through a node. The node may reject it before inclusion, keep it pending, or relay it. A block producer selects transactions and orders them. Execution applies their rules to the preceding state. An explorer displays an interpretation of this process, sometimes with a delay or incomplete indexing.
Boundaries and common mistakes
A transaction identifier is not proof of success. On an execution chain, a transaction can be included but revert: requested state changes are rolled back while execution fees can still be charged. A token transfer can also depend on contract behavior. Check the network, receipt status and relevant events, then distinguish technical success from the intended economic outcome.
The mechanism at a glance
- 01Prepare and sign
- 02Pending or rejected
- 03Include and execute
- 04Verify result and finality
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
A wallet prepares a request, obtains a signature and broadcasts it through a node. The node may reject it before inclusion, keep it pending, or relay it. A block producer selects transactions and orders them. Execution applies their rules to the preceding state. An explorer displays an interpretation of this process, sometimes with a delay or incomplete indexing.
Put the mechanism into context
A swap appears in a block with a failed receipt because its minimum output was not met. The user paid gas but received no swapped tokens. Build a timeline with submission, inclusion, execution result and later confirmation. Do not label the whole timeline simply “sent”.
Apply it in the workshop →What this mechanism does not guarantee
A transaction identifier is not proof of success. On an execution chain, a transaction can be included but revert: requested state changes are rolled back while execution fees can still be charged. A token transfer can also depend on contract behavior. Check the network, receipt status and relevant events, then distinguish technical success from the intended economic outcome.
The distinction that changes the analysis
A wallet can show a transaction identifier immediately after submission. That identifier lets you look up the attempt; it does not certify execution. Build a status timeline and attach separate evidence to submission, inclusion and the execution result.
Explain it yourself
Revisit the case above. Name what is established, what remains to be checked and the evidence needed to conclude. A strong answer addresses both sides of the diagram.
Apply the lesson to a case
A swap appears in a block with a failed receipt because its minimum output was not met. The user paid gas but received no swapped tokens. Build a timeline with submission, inclusion, execution result and later confirmation. Do not label the whole timeline simply “sent”.
Record chain, transaction hash, receipt status, balance changes and failure reason where available. Confirm that the first attempt really failed rather than remaining pending. A blind retry can duplicate an action. A new attempt also faces new prices and fees, so the previous quote is not a guarantee.
Follow a Bitcoin transaction
Wallet
Select available UTXOs, recipient, change and a fee. This simulation never connects to a wallet.
Terms in this lesson
- Finality
- The confidence or protocol guarantee that an accepted history will not be reversed, under stated assumptions.
Prepare a correction note
Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.