Transaction safety inspector
Parse a transaction or PSBT in your browser and read its inputs, outputs, and signature scope before you sign.
Protocol behavior Verified 2026-08-31
Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.
- Page ID
-
tools/transaction-inspector - Normative authority
- Executed source code at a pinned revision
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone, holder, developer
- Owner
- bitcoin-universe-docs
- Sources
-
- Atomicals ElectrumX
at
v1.5.2.0
- Atomicals ElectrumX
at
- Known limitations
-
- Parses locally and queries nothing. It cannot know which inputs are coloured unless you supply that.
- Explanatory. It is not the active validator and never a substitute for one.
- It never signs, broadcasts, or asks for key material.
このコンテンツはまだ日本語訳がありません。
Transaction safety inspector
Parses locally. Nothing is uploadedPaste a transaction to see its inputs, outputs, and the risks they carry.
Explanatory only. It is not the active validator and it is not a substitute for one. Anything it cannot determine is reported as unknown rather than guessed.
What it tells you
Section titled “What it tells you”| Reads | From |
|---|---|
| Version, and whether the transaction is segwit | The serialisation |
| Every input outpoint and sequence | The serialisation |
| Every output value, in order | The serialisation |
| The script kind per output | Script shape recognition |
| Declared signature hash types | The PSBT input maps |
| Expected allocation and burns | The allocation engine, if you supply the coloured inputs |
What it cannot tell you
Section titled “What it cannot tell you”- Whether an input is actually coloured. It queries nothing, so you must supply that.
- Whether the counterparty’s validator agrees.
- Whether the transaction will be accepted by a mempool.
- Whether an unrecognised script is safe. Unrecognised means unknown, not fine.
It fails closed: anything it cannot determine is reported as unknown rather than assumed.
The checks to run with it
Section titled “The checks to run with it”- Confirm every input outpoint is one you meant to spend.
- Confirm every output script and value matches your intent.
- Confirm the output order matches what you modelled.
- Confirm the signature hash type is the one you expected.
- Supply the coloured inputs and confirm the burn figure is zero.
See verify a transaction for the full procedure, including what to do after broadcast.