Fee needs prevouts
An exact fee requires a trusted amount for every spent output. A witness UTXO record is displayed, but for legacy inputs it must not replace full previous-transaction verification in a signing wallet.
Tools · Privacy-first
Inspect a Partially Signed Bitcoin Transaction before sharing it or opening it in a wallet. The read-only parser supports PSBT v0 and v2, inventories inputs, outputs, UTXO amounts, fees, signatures, locktime, transaction mutability, key origins, global xpubs, and opaque fields.
The inspector never asks for a private key and contains no signing, finalization, combine, broadcast, or mutation controls. A successful structural decode is not proof that the transaction is safe to sign.
Your PSBT stays in this browser.
Local input: PSBT Base64 or hex and a network used only to format recognized scripts as addresses. Network effect: None when inspecting. PSBT bytes and wallet metadata are processed in this page and are not sent to BitcoinStats, a node, an explorer, analytics, browser storage, or the URL.
Local input
Base64 and hexadecimal encodings are accepted up to 16 MiB. The network selector only changes how recognized output scripts are displayed as addresses.
Nothing is uploaded. Parsing starts only when you press “Inspect locally”.
Inspection result
Transaction summary
Both export actions reproduce the exact decoded input bytes. The inspector does not normalize or rewrite the PSBT.
Review signals
Input maps
Output maps
Privacy metadata
Key origins and extended public keys can reveal wallet structure and link transactions. Unknown and proprietary fields may contain additional application-specific metadata that this page deliberately does not interpret.
Purpose and limits
An exact fee requires a trusted amount for every spent output. A witness UTXO record is displayed, but for legacy inputs it must not replace full previous-transaction verification in a signing wallet.
The fee is available as soon as every prevout amount is known. Exact sat/vB is shown only when every input is finalized and the final transaction can be reconstructed.
Signature fields are counted, not verified. The page does not execute scripts, confirm change ownership, evaluate chain state, or decide whether a wallet should sign.
Parsing follows BIP174, BIP370, and BIP371 using a locally bundled, version-pinned @scure/btc-signer read-only parser path.