PSBT and raw transaction inspection

Transaction Doctor

Local parsing

Find missing data and inspect what a transaction actually contains.

Taproot Assets: anchor versus asset proof.

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

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

Copied from Lightning Labs' official regtest proof test vector, not created or mined by BitcoinSignetFaucet.com. Synthetic regtest assets; no public Signet or mainnet confirmation is claimed.

Taproot Assets: anchor versus asset proof

Inputs
1
Outputs
2
Fee
Unknown
Signed size
Unknown

Taproot Assets: first-itestbuxx

Bitcoin anchor output
1000 sats
Companion asset amount
1500 asset units
Encoded proof
1039 bytes

Lightning Labs regtest vector. Asset quantities come from the companion record, not the Bitcoin transaction. The asset proof, commitment, history, and ownership have not been verified.

Encoded asset proof · Companion vector · Pinned Lightning Labs source

  • 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.

  • TAPROOT_ASSETS_FIXTURE

    Exact bytes match Lightning Labs' official regtest Taproot Assets genesis-anchor fixture. Asset context comes from its pinned companion vector, not from recognizing a P2TR script.

  • ASSET_UNITS_NOT_SATS

    The companion record reports 1500 asset base units of first-itestbuxx. Bitcoin output 0 holds 1000 sats. These are different quantities; raw anchor bytes do not contain the asset amount.

  • ASSET_PROOF_NOT_VERIFIED

    The companion encoded asset proof is available as a reference artifact only. Doctor does not decode or validate Taproot Assets proofs, commitments, issuance history, or ownership. This Bitcoin anchor alone cannot establish them.

  • 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.

Read the missing-data report

Presence is not validity

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

Compare PSBT stages

Before a real broadcast

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

Bitcoin Core validation reference