Tag Archives: output

Looking at Bitcoin transactions


In this article I will explain what are the contents of a Bitcoin article and also try to break some common misconceptions about Bitcoin.

Bitcoin is the common name for a currency, a ledger and the protocol by which this ledger is shared and secured between participating nodes. This is an important distinction.
A transaction is a message in the Bitcoin Protocol, that describes a change in the Bitcoin Ledger and may, or may not be used to send Bitcoin Coins somewhere else.
Confused yet?

The bitcoin protocol consists of rules about transaction validations and methods for communicating the transactions with other participants.
The second part can be ignored for now. It is not the focus of this article.
The first part – the validations – must remain the same for all nodes that participate in the same network. If any node has different validation rules, even by a bit, it is likely to isolate itself by forking itself from the network. (There are exceptions to these rules, in the form of soft forks, but for the sake of simplicity, we will ignore this for now.)

A common misconception is that part of the validation is to see if the message is coming from the person who has the coins that are being spent. This is wrong for multiple reasons:
– not all coins are locked in addresses
– the validation of an address (or even the fact that addresses exist) is not something that the validation logic of transactions is concerned with

To understand that, you need to understand what a transaction consists of.

Size Field Description

4 bytes


Specifies which rules this transaction follows

1–9 bytes (VarInt)

Input Counter

How many inputs are included



One or more transaction inputs

1–9 bytes (VarInt)

Output Counter

How many outputs are included



One or more transaction outputs

4 bytes


A Unix timestamp or block number

The first things to verify is the version of the rules is supported, and if the transaction is properly formatted (and not some gibberish like “np3r3h8hr3hn293…”).
Once a transaction is parsed as valid object, the Inputs and Outputs are checked.
If all the inputs exist and their consumption is valid, and all the outputs don’t spend more than the total of the inputs, then the transaction is valid.
Lastly, the validators check the Locktime to see if the valid transaction can be spent yet. If so – they include it in a block. If not – it becomes invalid and gets ignored.

But lets look a bit deeper.

inputs and outputs

Simply explained, inputs are the money you use in your transaction, and outputs are the money you produce out of that transaction.

An everyday example would be when Alex wants to buy a new shirt from the store. The shirt costs 34.99 euro. Alex pays 2 bills of 20 euro each.
The inputs are the 2 bills of 20 euro. Each input has it’s own history. They are 2 separate inputs.
The outputs are 2 as well. The first output is the 34.99 that the shop receives. The second output is the 5.01 that Alex gets as change.

Bitcoin Inputs and outputs are very similar to that example.
After the transaction is done, it’s outputs can become inputs for other transactions.

Each input contains a script that specifies the rules for spending it. This script is written in the Bitcoin Script programming language.

It is a common misconception that the Bitcoin ledger and protocol have addresses, balances and keys. This is not true. These things are an abstraction of the bitcoin scripting subset accepted as standard. In other words the bitcoin scripting language (which allows you to do all sorts of cool stuff with your bitcoin) is ignored in most wallet applications, except if it is in one of a few very strict formats. This limitation of capabilities greatly improves the simplicity of writing and using a bitcoin wallet.
It is a good thing.

When somebody wants to consume an input, he simply has to provide an unlocking script, that goes before the script of the input itself.
If the script of the input is written with a meaning like “X… + 3 should equal 5” (X is the unlocking script) then the correct unlocking script would be “2”, because 2 + 3 = 5
In this example one doesn’t need to know any private keys, but simply needed to point to the input he wants to consume and give an unlocking script that matches the locking one.

The simplest example of a standard transaction is the P2PKH (pay to public key hash) transaction.
In it, the script meaning goes like that:

“Xsig, Xpubk… hash160 of Xpubk should equal <expected hash> and Xsig should be a signed message of Xpubk’s private key

Xsig, Xpubk are the expected values from the unlocking script.
Xpubk  proves that we know which public key corresponds to the <expected hash> that is hardcoded in the script
Xsig proves that we posses the private key corresponding to that public key

This is where the misconception about addresses originates from.

Now lets look at the contents of an Input:

Size Field Description

32 bytes

Transaction Hash

Pointer to the transaction containing the UTXO to be spent

4 bytes

Output Index

The index number of the UTXO to be spent; first one is 0

1-9 bytes (VarInt)

Unlocking-Script Size

Unlocking-Script length in bytes, to follow



A script that fulfills the conditions of the UTXO locking script.

4 bytes

Sequence Number

Currently disabled Tx-replacement feature, set to 0xFFFFFFFF

As you see the input data in the transaction doesn’t actually contain the input itself. It simply points to an Output Index. Since all bitcoin participants agree on the state of the blockchain, the unconsumed transaction outputs (UTXO) would be the same for all of them. An index is enough to find the needed data. The Input data however must provide an unlocking script.

SCRIPT Validation

When is a script valid?

When it executes to the end and the final value is “TRUE”.
If a script ends with a different result, or if it gets interrupted due to wrong usage of it’s methods, it is invalid, and therefore – the input becomes invalid and can not be consumed.

The output scripts also get validated, but they don’t get executed (since their unlocking script is missing). Instead, an output script validation simply checks if what was written is within the syntax of the bitcoin scripting language.

If all inputs and their scripts are valid and the outputs are valid too, and the sum of the consumed coins from the inputs is greater or equal to the sum of the coins in the outputs, then a transaction can be valid.

This is all for now.

This was a simplified article, aiming to explain basic concepts like Script, UTXO, Inputs and Outputs

Go to my article about bitcoin-cli usage and try looking at some transaction data with it.
Experimentation is the most interesting way of learning

You could also read this chapter of the “Mastering Bitcoin Cash” book : https://developer.bitcoin.com/mastering-bitcoin-cash/transactions.html

In the next post I will try to explain the syntax of the Bitcoin Script programming language and how to write your own scripts.

Study hard. Bye!