How Does a Bitcoin Transaction Work?

Bitadvocate Editorial Team
·
Updated September 17, 2026
·
approx. 7 min read

A Bitcoin transaction is an order you sign with your private key and post to the network. In effect it says: certain amounts that belong to me should now belong to someone else. The nodes check the signature, a miner packs the order into the next suitable block, and from that point it has its first confirmation.

One thing first: you are not moving a number from one account to another. You spend earlier amounts in full and get the rest back as change, much like paying with a banknote. This walkthrough covers why a transaction carries a fee and why the sensible wait depends on the amount and the situation, not on a fixed rule.

How current is this?Last checked: 17 September 2026

Rules and supervisory practice change. The statements reflect the state of things on the date given above and are not legal or tax advice.

What happens in a transaction

The Bitcoin whitepaper describes Bitcoin as a chain of digital signatures. Each owner hands an amount to the next by signing a reference to the previous transaction together with the recipient’s public key. Anyone who checks the signatures can follow the unbroken chain of ownership.

Your wallet does this in the background. It chooses which earlier amounts to spend, builds the outputs to the recipient and back to yourself, signs the lot and sends it to the network. There each node takes the order into its own waiting area, the mempool. There is no single central mempool; every node keeps its own. Miners pull transactions from it into the next block.

Worth remembering: A transaction is not an account transfer. It is a signed proof that you may spend certain earlier amounts, together with instructions on who they belong to from now on.

Inputs, outputs and change

Bitcoin has no balances, only unspent earlier outputs. When you pay, your wallet takes one or more of them as inputs and spends them in full. According to the Bitcoin whitepaper, a normal transaction has either a single input from a larger earlier transaction or several small inputs, and at most two outputs: one for the payment and one sending the change back to you.

An example. You want to send 0.02 bitcoin and your wallet holds an earlier receipt of 0.05 bitcoin. It spends the whole 0.05, sends 0.02 to the recipient and roughly 0.03 back to an address of your own as change. The small remainder that reaches neither the recipient nor the change output is the fee.

Comparison: Much like paying with a banknote. You have no exact amount, so you hand over a larger note and get change back. Here the change simply goes to an address of yours, usually a fresh one.

Where the fee comes from

The fee is not a fixed charge, just the leftover. The Bitcoin whitepaper puts it plainly: if the outputs add up to less than the inputs, the difference is the transaction fee, and it goes to the miner who finds the block.

  • You set the amount in practice, through your wallet. A higher fee makes it more likely your order lands in a block sooner.
  • The cost tracks the size of the transaction, measured in virtual bytes (vB), not the amount you send. Many small inputs make a transaction larger and so more expensive.
  • When the mempools fill up, fees rise because more orders compete for the limited space in the next block. In quiet spells it gets cheaper.

Fee rates are usually quoted as satoshis per virtual byte, sat/vB for short. For very small everyday amounts the detour over the Lightning Network is often worth it, since no individual blockchain transaction is needed there.

Confirmations and how long to wait

Once your transaction is in a block, it has one confirmation. Every further block built on top adds another. The Bitcoin whitepaper shows with numbers that the chance of reversing an already confirmed transaction falls quickly with each further confirmation.

A block takes about ten minutes on average, sometimes less, sometimes more. How many confirmations are enough for your case is not a fixed Bitcoin rule. It depends on the amount, on the counterparty, on how costly an attack would be for someone, and on the context. The overview below shows what each level means.

0 confirmations
State
The transaction is visible on the network but is not yet in any block.
What it means
It can still be replaced by a competing transaction paying a higher fee, a double-spend. Since Bitcoin Core 28.0, nodes with default settings accept such replacements without prior signalling. Not enough for anything that matters.
1 confirmation
State
The transaction is included in a block.
What it means
Reversing it now would already cost mining work. For small everyday amounts this can be enough, depending on the counterparty.
Several confirmations
State
More blocks have been built on top of the transaction’s block.
What it means
Each block makes a reversal less likely, because an attacker would have to redo the whole chain from that point on.
6 confirmations
State
About an hour has passed and six blocks have piled up.
What it means
A common conservative reference. The Bitcoin developer documentation itself calls the number somewhat arbitrary and recommends it for high-value payments. Not a magic line and not proof of absolute finality.

Exchanges usually set their own number of confirmations for deposits. Until it is reached, the amount is not yet available there.

Why a new address every time

You may notice that your wallet uses a fresh address for change and for every new receipt. The Bitcoin whitepaper recommends exactly that: a new key pair for each transaction so that payments cannot easily be tied to a person.

Every transaction is publicly visible. What is visible is that an amount moves from one address to another, not who owns the addresses. A fresh address per transaction keeps that separation intact. Reusing an old address is technically fine but links more payments together than it needs to. How wallets handle this is covered in the overview of wallet types.

Peer-to-peer, MiCA, and why you should label transactions

Applies across the EU. This section is based on EU law and therefore applies in Austria as well. Rules outside the EU differ. It is general information and does not replace legal or tax advice.

A common question: does a payment between two people fall under MiCA? Under Article 2(1), the Regulation (EU) 2023/1114 (MiCA) applies to persons engaged in the issuance, offer to the public and admission to trading of crypto-assets in the Union, or providing crypto-asset services. In other words, it addresses issuers, offerors and crypto-asset service providers.

If you hold your own bitcoin and send it directly to another person, no such service provider takes part in that. Recital 22 of the regulation states explicitly that crypto-asset services provided in an exclusively decentralised manner without an intermediary should fall outside its scope.

What does not follow: Peer-to-peer does not mean rule-free. The moment an exchange, a broker or a custodian is involved, MiCA and the Transfer of Funds Regulation (EU) 2023/1113 apply. And record-keeping and tax reporting duties are untouched by any of this.

This is where an unremarkable habit becomes valuable: label your transactions in your wallet as they happen. Many wallets allow a note per incoming and outgoing payment. The burden of showing where an amount came from later sits with you, not with the network.

What a good label contains
1

Date and reason
What the amount was for. An invoice, a gift, a repayment, a purchase through an exchange. A keyword is enough, as long as you still understand it in two years.
2

The counterparty, as far as you can name it
A name or a platform. For private payments a short code that is unambiguous to you is plenty.
3

Where the paperwork sits
Where the matching invoice, chat log or exchange statement lives. The label is the pointer, not the archive.
4

Acquisition date on purchases
For tax purposes, when an amount was acquired is the decisive fact. Reconstructing that later is far more work than noting it once.

A label is a note to yourself and is reported to no one. It stays local in your wallet. Its value shows up the moment you want to evidence an origin, whether to a regulated provider or in your tax return.

Conclusion

A Bitcoin transaction is a signed order that spends earlier amounts in full and hands the rest back as change. The fee is the gap between what goes in and what comes out, and it tracks the size of the transaction and how busy the network is, not the amount. After a transaction lands in a block, every further confirmation counts, and how many you wait for follows from the amount, the counterparty and the context rather than a fixed rule. For a daily coffee that is a lot of overhead, which is what paying day to day over Lightning is for.

Ready for the next step?

The using Bitcoin section walks through how Bitcoin works day to day, from sending and receiving to saving, with no product ranking and no pressure.

Go to the using Bitcoin section

Frequently asked questions about Bitcoin transactions

These tend to come up when someone sends their first transaction and wonders about the change, the fee or the wait. The answers follow the Bitcoin protocol as set out in the whitepaper and the reference software.

How does a Bitcoin transaction work, in plain terms?+

Your wallet picks earlier amounts that belong to you, spends them in full, sends the amount you want to the recipient and the rest back to you as change. It signs this with your private key and posts it to the network. The order waits in the nodes’ mempools until a miner packs it into a block.

Why do I get change in a Bitcoin transaction?+

Because Bitcoin has no balances, only whole earlier outputs that are spent in full. If none of them matches the target amount exactly, your wallet returns the surplus as change to an address of your own, usually a fresh one, much like paying with a larger banknote.

What does the transaction fee depend on?+

Not on the amount sent, but on the size of the transaction, measured in virtual bytes (vB), and on how busy the network is. Many small inputs make the transaction larger and more expensive. When the mempools are full, fees rise because more orders compete for the space in the next block. The fee rate is usually quoted as sat/vB.

How many confirmations do I need?+

There is no fixed Bitcoin rule. Zero confirmations means the transaction is not in a block yet and carries a real double-spend risk. One confirmation means it is in a block. Each further confirmation makes a reversal less likely. Six confirmations are a common conservative reference, not a magic line. How many you wait for follows from the amount, the counterparty and the context.

How long does a Bitcoin transaction take?+

To the first confirmation, about ten minutes on average, sometimes less, sometimes more, depending on when the next block is found and whether your fee is high enough for early inclusion. With a low fee and full mempools it can take considerably longer.

Can I reverse a sent Bitcoin transaction?+

There is no cancel button for the sender, unlike a bank transfer. Technically, though, a single confirmation is not absolutely final: in a very short chain reorganisation, a reorg, a freshly confirmed block can still drop out of the valid chain. Each further confirmation makes that quickly less likely. While the transaction is only waiting in the mempool, some wallets let you replace it with a higher-fee version. Do not rely on any of this; check the recipient address first.

Thanks for reading this far. If you are curious, take a look at the other Bitadvocate blog guides as well.

Sources

The statements above were checked against these primary sources.

Produced by the Bitadvocate editorial team. This article reflects the state of things when it was checked and is not legal, tax or investment advice.