Bitcoin transaction decoder

Paste a transaction ID to turn raw public-chain fields into a readable map. This tool never asks for a key, seed phrase or wallet connection.

Decode a public transaction

A TXID is public and contains 64 hexadecimal characters. Do not paste a private key, seed phrase, descriptor or unsigned transaction here.

Transaction ID

Waiting for a transaction ID.

Confirmation—

Inputs / outputs—

Virtual size—

Fee rate—

Decoded outputs

#	Address or script	Type	Value
Decode a transaction to inspect its outputs.

Read the shape before the story

A transaction proves that valid inputs authorized new outputs. It does not explain why people moved the coins. One payment may include change; many outputs may be a batch; one input may represent years of earlier activity.

Fee rate is fee divided by virtual size

The total fee is the input value minus the output value. Miners compare fee rate in sat/vB because a small transaction and a large transaction compete for different amounts of block space.

Use the UTXO planner to model a similar shape or open the fee explorer for current block-space conditions.

What the fields mean

Version	Transaction serialization rules used by the sender.
Locktime	A height or time condition; zero usually means no locktime.
Sequence	Can signal relative locks or replace-by-fee behavior.
Weight	Bitcoin’s accounting measure for block capacity.
Confirmations	Depth grows as blocks are added after inclusion.

Public does not mean identity

Addresses are pseudonymous. Avoid labelling a person from transaction shape alone. Chain-analysis guesses can be wrong.

How Bitcoin.now handles tool data

Calculated values

Deterministic tools state their assumptions beside the result. They do not present a model as an executable quote.

Observed values

External observations use read-only public data, retain the latest valid cache, and show freshness when a source is delayed.

Safety boundary

No tool trades, broadcasts, connects a wallet, stores a secret, or gives personal financial advice.

Review the data methodology, editorial policy, and risk disclaimer.

Using bitcoin transaction decoder responsibly

Can a TXID reveal the sender?

A transaction reveals scripts and coin movement, not a verified real-world identity. Labels from explorers or analytics firms are claims that need separate evidence.

Why is an output probably change?

Change detection is a heuristic. Wallet behavior, batching and script types may offer clues, but the chain does not mark one output as payment and another as change.

Can this tool broadcast a transaction?

No. It performs a read-only lookup of an already public TXID. There is no raw-transaction upload, signing, wallet connection or broadcast endpoint.

Read a transaction the way a node does

The decoder fetches a transaction by its 64-character ID from public explorers and lays out the fields a node validates: inputs, outputs, size, weight, fee and confirmation status. Nothing is estimated; every number is on the chain.

Fee is the gap between inputs and outputs

A transaction does not name its fee. Miners keep whatever input value is not assigned to an output, so the decoder sums both sides and shows the difference, then divides by virtual size to give the rate the sender paid.

Input value comes from the outputs being spent, so the decoder resolves each one.
Fee rate in sat/vB is what to compare with the mempool at the time it was sent.
A coinbase transaction has no inputs; its outputs are the block reward.

How transactions are built →

Weight, size and vsize are three views of one thing

Size is raw bytes. Weight counts witness bytes at a quarter of the rest. Virtual size is weight divided by four, rounded up, and is the unit fees are charged on. A SegWit transaction has a vsize well below its byte size.

Blocks hold 4,000,000 weight units, about 1 MB of non-witness data.
A version-2 transaction with locktime 0 is the modern default.
Sequence numbers below 0xFFFFFFFE signal replace-by-fee.

Transaction fee, defined →

Fields the decoder shows and what they mean

Field	Meaning	Where it comes from	Common misreading
txid	Hash identifying the transaction	Computed from the transaction bytes	A payment reference — it is not, until confirmed
vin / vout	Coins spent and coins created	Previous outputs; new locking scripts	Change outputs are payments to someone else
fee_rate	Fee ÷ virtual size	Derived from resolved inputs	Fee as a percentage of the amount
confirmed / block_height	Included in a block, and which one	Explorer chain data	One confirmation is final for any amount