PSBT and raw transaction inspection

Transaction Doctor

Local parsing

Find missing data and inspect what a transaction actually contains.

Prepared example

Missing previous output. Fee unknown.

Base64 PSBT or raw transaction hex Open a PSBT or transaction file

Parsing stays in this browser. No keys or recovery phrases. PSBT v0 only; a parsed file is not a validation verdict.

Look up a public Signet transaction

Transaction ID

This explicit lookup sends the txid and your IP address to mempool.space. It does not broadcast anything.

Synthetic offline fixture. Outpoints are invented, not mined, broadcast, or confirmed. Never fund example addresses.

MISSING_UTXO
Previous output amount and script are absent; fee and signing prerequisites remain unknown.
MISSING_SIGNATURES
No partial signatures or final unlocking fields are present; script requirements were not evaluated.
UNSUPPORTED_SIZE_ESTIMATE
No signed-size estimate for this input script or missing script metadata.
FEE_UNKNOWN
The fee cannot be calculated without every previous output amount.
TIMELOCK_UNCHECKED
Locktime/sequence constraints are present. Chain height, median time, and input ages were not checked.
NOT_VALIDATED
Parsing and metadata inspection only: no signature/script verification, finalizability decision, UTXO-set check, or mempool test.

Signature validity, spendability, and mempool acceptance have not been checked.

Input details

Output details

Locktime, sequence, and transaction identifiers

Locktime and sequence constraints need chain context. RBF signaling does not guarantee that a replacement is accepted.

An unknown fee is useful

Missing previous-output values must not turn into a made-up zero fee. Parsing a PSBT and having enough data to sign it are different milestones.

A signature field, or even final witness data, is not proof that every script condition is satisfied.

A signer checks authorization. A node checks consensus and current policy. Confirmation is a later observation.