Transaction Input

Overview

What it means and why it exists

A transaction input identifies coins or another spendable resource that a transaction uses as its source. On Bitcoin, an input refers to an earlier unspent output; it is not simply an amount typed into a payment form.

How it works

A Bitcoin sender selects one or more existing UTXOs, points each input to its earlier transaction ID and output index, and supplies unlocking data such as a signature. The network checks that the referenced output exists, is still unspent, and can be spent under its locking conditions. Input values, minus output values, determine the fee.

Technical details worth understanding

Inputs help explain why a wallet showing one BTC may spend several smaller pieces rather than a single balance. Adding inputs increases transaction weight and potentially the fee. Bitcoin-style inputs differ fundamentally from account-based Ethereum transactions, which debit an account balance and advance a nonce.

What can go wrong

A signed input does not guarantee confirmation. An already-spent reference is invalid; a conflicting unconfirmed spend may be replaced or rejected depending on policy. Never identify the paying customer from an input address alone, because exchanges and custodians often send from pooled wallets.

Practical checks

When investigating a BTC transfer, open the raw transaction and identify every previous output it spends. Check whether any input is also referenced by a competing unconfirmed transaction. This is especially useful when a payment appears in a mempool but later vanishes. A sender's input addresses need not identify the purchaser.

Related concepts

Blockchain, Bitcoin (BTC), Transaction Hash.

Further reading

Bitcoin Developer Guide — Transactions.