Rovereto, Thursday 19 November 2026 · Year XIII, n. 323
en
Bitcoin Valley
ContentsClose

Dispatches from the valley where you pay in bitcoin.

Learn · Lesson 3 · In depth

Looking in the ledger

Bitcoin's ledger is open to everyone. With an explorer you read it yourself: a payment, its confirmations, what has really arrived.

The ledger is public, and anyone can read it. An explorer is a website that lays it out in pages: you search for a payment or an address and it shows you what's recorded there. Two of many are mempool.space and blockstream.info. They all read the same ledger: use whichever you find easiest. We have one here too: inexp, the explorer born at inbitcoin, where the site does the searching for you.

Lightning payments don't show up there, because they happen off the ledger: at most you'll see a channel opening or closing. What you can see are on-chain payments, the ones sent to a Bitcoin address like bc1q….

In the search box you paste the address, or the transaction ID, the txid: 64 characters your wallet shows in the payment details.

How to read a transaction

Confirmations. “Unconfirmed” means the transaction is waiting in the mempool, the waiting room. When it gets into a block it has one confirmation, and each block after that adds another, roughly every ten minutes. How many to wait for depends on the amount and on who's paying: the maths is in lesson 8.

An example transaction, in round numbers: the same one we go through below, line by line.

An example, in round numbers satoshis
Input: bitcoin received earlier, not yet spent 100,000
Output: to the recipient 30,000
Output: the change, back to the payer 69,000
Fee: the difference 1,000
100,000 satoshis received earlier and not yet spent go in whole and split three ways: 30,000 to the recipient, 69,000 in change back to the payer, and 1,000 in fees to the miner.100,000SATreceived, unspent30,000to the recipient69,000change, to the payer1,000fee, to the miner
The same transaction, drawn: the input is spent whole and splits, each band as wide as its share. The thin red slice is the fee, drawn a little thicker: to scale it would be a hairline. Real transactions look like this on inexp.

Inputs and outputs. A bank transfer has one sender and one recipient. A Bitcoin transaction, as one of our course slides put it, “has n ‘senders’ and m ‘recipients’”.1 The inputs are bitcoin received earlier and not yet spent (UTXO): like a banknote, they're spent whole. The outputs are the new amounts that come out of them, and they stay there until someone spends them in turn.

Change. It's like paying for a coffee with a twenty-euro note: the whole note goes, and you get change back. So usually one output goes to the recipient and another goes back to the payer, at an address of their own. Almost always it's a new address, not the one the satoshis came from: that's not a mistake, it's the wallet doing its job. The explorer doesn't know which of the two is the change. Your wallet does: it knows all its own addresses.

The fee. It isn't an output: it's what's missing. Add up the inputs, subtract the outputs, and the difference goes to the miner who writes the block. It doesn't depend on the amount: it depends on how much space the transaction takes up and how busy the mempool is. The explorer also shows it in satoshis per virtual byte, sat/vB.

What those looking can see. On the ledger there is no name of yours: there are addresses. Bitcoin is pseudonymous, not anonymous. If an address gets tied to you, because you gave it to a shop or wrote it in a post, from there people can follow what passed through it. That is why the wallet creates a new one for every payment you receive, as Satoshi's text already advised.2 Receiving on the same one every time is called address reuse, and it's best avoided: it lines up your payments in front of anyone who knows that address, meaning the people you gave it to and anyone who finds it in that post. With a new address each time, the person who paid you finds their own payment, not the line of everyone else's.

Checking a payment you've received

  1. Copy from your wallet the address you gave the person paying.
  2. Search for it in the explorer and open the incoming transaction.
  3. Look at the output to your address: that's the amount you're receiving, not the transaction total.
  4. Check the confirmations. While there are none, the payment isn't recorded yet.
  5. Your wallet should say the same thing.

A screenshot or a link sent by the person paying is not proof. Look it up yourself, with your own address.

Searching privately

When you look up an address, the site showing it to you sees the query and your IP address, and can link the two: as far as it's concerned, that address and its balance are now yours. If you'd rather keep that to yourself, there are three easy options:

  • an explorer running on your own node: you already have the ledger, so you don't have to ask anyone for anything;
  • Tor, which hides your IP from the explorer;
  • a watch-only wallet, which follows an address without being able to spend from it. It gets its data from a server, or from your node if you have one.

Lesson 3: the first wallet An explorer on your own node How many confirmations are enough


  1. Slide from the Basics course, March 2025, no. 8. ↩

  2. Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, 2008, §10 (the text): “a new key pair should be used for each transaction to keep them from being linked to a common owner”. Slides of the Basics course, March 2025, no. 15. ↩