PSBT Inspector

What this tool does

Before signing a PSBT received from a third party (marketplace, OTC counterparty, multi-sig…), run it through the Inspector. It decodes the PSBT locally, enriches inputs (Ordiscan), simulates sat flow, computes a safety score and offers an optional AI audit.

When to use it

• PSBT received from an ordinals marketplace (Magic Eden, Gamma…).
• OTC trade of an inscription, rune or rare sat.
• Multi-sig: audit before signing.
• Debugging a PSBT you built yourself.

Prerequisites

• No wallet required (read-only).
• Ordiscan key for full input enrichment.

Step-by-step

1. Paste your PSBT (binary, base64 or hex) or upload the file.
2. Decoding is local and instant.
3. Read the Safety Score and the list of automatic checks.
4. Asset Diff tab: what you give up vs what you receive.
5. Fee Intelligence tab: effective fee rate, comparison to mempool tiers.
6. Flow tab: inputs → outputs diagram with annotated sats.
7. Optional: AI Audit for a natural-language summary of risks.

Edge cases

• Inscription sent to a payment address: risk of spending it as fee later → blocking warning.
• Rare sat in the fee: critical warning.
• Cenotaph rune: rune burned → red check.
• Dust outputs: below the threshold → the tx won't be relayed.
• Fee rate outside the 1–300 sat/vB range: warning.
• Ordiscan quota exhausted: banner + partial enrichment.

Safeguards

• Decoding is fully local — your PSBT does not leave your browser (unless you click AI Audit).
• Consistency check on sat-flow input ↔ output.
• Automatic detection of signatures already present (Signature Status panel).

Data sources

• Ordiscan: input enrichment (sat-ranges, inscriptions, runes).
• mempool.space: reference fee-rate tiers.
• Supabase Edge Function analyze-psbt: only when you click “AI Audit”.

Server side

Without clicking AI Audit: no server call other than the Ordiscan enrichment. With AI Audit: the decoded JSON payload (amounts, addresses, types) is sent to the Edge Function. No key, no seed, no PII.