Follow a Bitcoin Transaction Backward and Forward### See where its inputs came from, which outputs it created, and where spent outputs moved next
A Bitcoin wallet usually gives you the result: a payment was sent, received, or confirmed.
That is enough for everyday use. But it hides the structure underneath.
A Bitcoin transaction is not simply a transfer from one account to another. It consumes outputs created by earlier transactions and creates new outputs that may be spent later. Every confirmed transaction therefore sits between a visible past and a potentially traceable future.
Bitcoin Transaction Tree makes this structure visible.
Paste a transaction ID, and the transaction becomes the center of an interactive graph. Its inputs appear on the left. Its outputs appear on the right. If an output has already been spent, you can continue to the transaction that spent it. Select any connected transaction and it becomes the new center.
The result is not a static explorer page. It is a way to move through Bitcoin’s transaction history one connection at a time.
Start With a TXID
Every Bitcoin transaction has a transaction ID, usually called a TXID. It is a 64-character hexadecimal identifier derived from the transaction data.
Enter a TXID into Bitcoin Transaction Tree and the app loads the corresponding public blockchain data.
The center card shows the selected transaction, including:
- total output value,
- number of inputs and outputs,
- confirmation status,
- transaction fee and fee rate,
- size, weight, and virtual size,
- block height and mining time. The surrounding cards explain how that transaction connects to the rest of the network.
Follow the Transaction Backward
An input does not merely contain an address and an amount. It references a specific output from an earlier transaction.
Bitcoin Transaction Tree labels that connection as the Previous TXID. Select it and the earlier transaction moves into the center.
This lets you answer questions such as:
- Was the payment funded by one previous output or many?
- Were several smaller UTXOs combined?
- Did the funds originate from a much larger transaction?
- How far back can the visible chain of transactions be followed? Some transactions have one input. Others combine dozens or even hundreds. The app keeps large transactions manageable by initially showing only part of a long list and allowing the rest to be expanded.
Follow the Transaction Forward
Every output has one of two basic states:
- Unspent: the output is still a UTXO and can be used in a future transaction.
- Spent: a later transaction has already consumed it as an input. For a spent output, Bitcoin Transaction Tree shows the Spending TXID. Select it to move forward to the transaction that used those coins.
You can therefore begin with yesterday’s wallet payment and continue into its later history — provided the relevant output has been spent.
This is particularly useful when a wallet shows only the original payment. The tree reveals the technical structure around it: the funding input, the payment output, a possible change output, and any later spending transaction.
A Real Payment Is Often More Than One Payment
Suppose a transaction consumes an input worth 22,352 satoshis and creates two outputs:
- 10,000 satoshis to the recipient,
- 10,943 satoshis returned as change. The remaining 1,409 satoshis are the miner fee.
A wallet may simply display “Received 10,000 sats.” The transaction tree shows how that result was constructed.
This distinction matters because Bitcoin does not maintain account balances inside the blockchain. Wallet software calculates a balance by finding the unspent outputs it can unlock.
Useful Beyond Education
The visual approach is valuable in classrooms, but it is not limited to education.
Bitcoin users can inspect their own payments. Merchants can understand how a received transaction was assembled. Developers can verify assumptions about wallet behavior. Analysts and journalists can follow publicly visible transaction relationships without manually opening a new explorer page for every TXID.
The app is also useful when explaining:
- consolidation of many small UTXOs,
- change outputs,
- unusually high transaction fees,
- old transactions with very large Bitcoin amounts,
- transactions that fan out into many outputs,
- the difference between an address and a transaction. ### What the Tree Does Not Prove
Bitcoin’s ledger is public, but public does not mean identified.
A connection between transactions proves that one output was later used as an input. It does not automatically reveal the person or organization controlling an address. Multiple addresses may belong to one wallet, and one service may create transactions for many unrelated users.
The tree shows value flow, not verified identity.
That limitation is important. A useful blockchain tool should make public evidence easier to inspect without presenting guesses as facts.
Read-Only by Design
Bitcoin Transaction Tree does not contain a wallet. It does not request private keys or recovery phrases, and it cannot send, receive, buy, or sell Bitcoin.
It reads public blockchain data and stores previously inspected transactions in a local cache. Navigation history lets you move backward and forward through your exploration, while the original-transaction button returns to the TXID where you started.
Sometimes a wallet tells you what happened. A block explorer gives you all the raw details. Bitcoin Transaction Tree sits between those two views: it shows what happened and how one transaction connects to the next.
Download on App Store: https://apps.apple.com/us/app/bitcoin-transaction-tree/id6811372344
More Beaver Tools: https://beavertools.app/
More Bitcoin Apps: https://btcminertools.com/
Top comments (0)