How can you connect the pieces?
Start with keys if you want to understand authority, transactions if you want to follow a payment, or blocks if you want to understand mining. You can read each lesson on its own; there is no account or required course sequence.
What is inside transactions?
- How does the UTXO model represent your bitcoin?
- What do transaction inputs and outputs contain?
- How do vbytes turn a fee rate into a fee?
- Why does a Bitcoin payment often create change?
- Bitcoin basics
- How does Script decide whether an output can be spent?
- How do absolute and relative timelocks differ?
- Which sample outputs can fund your payment?
- What fee follows from your chosen size and rate?
What is inside blocks and mining?
- What does SHA-256 do to its input?
- What happens when you change a hash input?
- What does a Bitcoin block header commit to?
- How do proof of work and difficulty fit together?
- How does the halving change Bitcoin’s subsidy?
- How does a Merkle tree commit to transactions?
- Which subsidy applies at your chosen block height?
What is inside bitcoin family decoded?
How would you investigate an unfamiliar fee?
Start with Transactions, then read fees and vbytes. Follow the related link to the mempool explanation when you want to understand waiting. The fee unit and the confirmation process answer different parts of your question.
Where are the site information pages?
Bitcoin Decoded home introduces the publication. Read how your information is handled before using the email learning form.
Which references support this reading map?
Sources: Transaction developer reference; Block chain developer guide.