Ordinals Wallet Inspector

Yes — always move valuable assets out first before merging anything. Follow the steps below in order. Skipping steps or merging before everything has loaded can result in permanent loss of inscriptions, Runes, or rare sats.

Runes (the Bitcoin token protocol by Casey Rodarmor) are stored inside UTXOs. When a Rune is transferred, the transaction typically produces two separate outputs:

546 sats is Bitcoin's dust limit — the minimum a UTXO can hold without being rejected by the network. Rune wallets use this minimum to keep fees low.

The two UTXOs are linked by the transaction that created them, but on-chain they are independent. An OP_RETURN output in the same transaction (called a runestone) specifies exactly which output index receives which Rune amount.

⚠️ Do not merge or spend either UTXO carelessly — spending the wrong one will permanently destroy your Rune balance. Always use a Rune-aware wallet such as Xverse or UniSat.

No — an Ordinal inscription lives in exactly one UTXO. Although creating an inscription requires a two-step commit/reveal process, once that is complete only a single output remains, and that is the UTXO you see in your wallet.

The inscription is permanently attached to the first sat in that UTXO (offset 0). Wherever that UTXO is spent, the inscription travels with it.

The UTXO may contain more than 546 sats — the extra sats are padding added by the wallet or sender. This inspector classifies them by size:

The "extra" sats are locked alongside the inscription and cannot be spent separately. To recover them you must send the entire UTXO through an Ordinals-aware wallet that preserves the inscription sat at offset 0.

Merging Rune UTXOs without a Rune-aware wallet will permanently burn the Rune tokens. A standard merge transaction contains no runestone (the OP_RETURN instruction that tells the Rune protocol where to send the balance). Without it, the protocol considers the tokens destroyed — this cannot be undone.

Once the Rune is burned, what remains is ordinary Bitcoin. You can send it to any address including a bc1q exchange address, and sell it — but you will only recover a few hundred sats after network fees, worth less than $1.

Before merging, check whether the Rune has value:

⚠️ This tool does not include a runestone when building merge transactions, so using it on Rune UTXOs will burn the tokens. Always use a Rune-aware wallet to transfer or sell Runes.

The exchange receives the sats — the inscription is permanently lost. Exchanges are not Ordinals-aware. To them it is just a Bitcoin deposit, and they will sweep it into cold storage without preserving the inscription.

Extra risks to be aware of:

Many exchanges have a minimum deposit threshold (often 10,000+ sats) — below that the deposit may be silently ignored and you lose everything with no credit. Additionally, once the exchange sweeps the UTXO into their cold storage wallet, you cannot claim it back.

What to do instead:

What "exchange sweep" means: the address an exchange gives you is a temporary deposit address. Within minutes an automated system moves your deposit into the exchange's main cold storage wallet — this is called a sweep. That sweep transaction has no Ordinals logic and simply moves the sats. Your inscription gets mixed in with millions of other UTXOs from other users and becomes permanently untraceable.

Think of it like dropping a rare coin into a cash register. The cashier only sees the face value. At the end of the day all coins are counted and bagged together — your rare coin is now in a bag with 10,000 others and impossible to find.

⚠️ Never send a valued inscribed UTXO directly to an exchange. For junk ordinals with no value the inscription loss does not matter — but always merge them first using this tool to recover the sats as clean BTC before sending anything to an exchange. Only send clean, inscription-free UTXOs to an exchange.

This tool only supports Taproot (bc1p) destination addresses. If you enter a bc1q address it will throw an error and no transaction will be built. You must use a bc1p address as the recipient.

Even if you send to a valid bc1p address, the result depends on what you selected:

💡 Tip: Use the Select Clean button in the toolbar to automatically select only safe, inscription-free UTXOs before sending.

A runestone is an instruction note embedded inside a Bitcoin transaction that tells the Rune protocol what to do with the tokens. It is written into a special field called OP_RETURN, which can carry data but holds no BTC.

A simple way to think about it:

Why this tool does not include a runestone: building a valid runestone requires knowing which Rune is being moved, the exact token amount, and which output receives them. This tool only reads UTXO data from mempool.space and has no knowledge of Rune balances or token amounts — so it cannot write a correct runestone. It deliberately leaves it out rather than risk writing a wrong one and destroying your tokens.

⚠️ Always use a Rune-aware wallet such as Xverse or UniSat to transfer or sell Runes. These wallets read the Rune balance, write the correct runestone, and ensure the tokens arrive safely.

Yes — the sats arrive as spendable Bitcoin, but check the inscription value first. A 33,000 sat UTXO sent to a bc1q address arrives as approximately 32,500 sats of spendable BTC after network fees. The receiving wallet sees it as plain Bitcoin and has no idea an inscription is attached — it will spend it as regular BTC.

33,000 sats classifies as a whale ordinal (≥ 20,000 sats). Someone padded it heavily — often because the inscription has real value. You could be selling a valuable inscription for just $27 worth of BTC.

Before sending, check the inscription value:

⚠️ Always check a whale ordinal's value before spending it as plain BTC.

No — it does not matter at all. After merging, the resulting UTXO at your bc1p address is completely clean plain Bitcoin. The inscriptions are gone. A common misconception is that bc1p means Ordinals and therefore cannot be sent to an exchange — this is not true.

The exchange does not care whether the BTC came from a bc1p or bc1q address — it simply sees the amount and credits your account. The flow is straightforward:

A sat (short for satoshi) is the smallest unit of Bitcoin. One Bitcoin equals 100,000,000 sats. All values in this tool are shown in sats because Ordinals, Runes, and other Bitcoin protocols operate at the individual sat level — each sat is unique and can carry an inscription or special attribute.

The dust limit is the minimum value a Bitcoin UTXO can hold without being rejected by the network as "dust" — an output so small it would cost more in fees to spend than it is worth. For Taproot (bc1p) outputs the dust limit is 546 sats. This is why Ordinal inscriptions and Rune UTXOs are always at least 546 sats — it is the smallest amount the Bitcoin network will accept as a valid output.

Satributes are special properties assigned to individual sats based on Bitcoin history or mathematics. Collectors pay significant premiums for sats with rare satributes — a single palindrome or nakamoto sat can be worth far more than its face value in BTC.

This inspector detects satributes automatically and displays them in the Satributes column. Always check this column before merging or sending any UTXO.

Both live inside Bitcoin UTXOs but they work very differently:

This is a UTXO consolidation — nothing has been lost, everything has just been merged into one output.

When your wallet sent that transaction, it used all of your UTXOs as inputs and produced a single output of 200,000 sats. The 7 inscriptions, which were previously spread across multiple UTXOs (totalling ~30,000 sats), plus your clean sats, were all swept into that one UTXO together.

Ordinal theory tracks individual satoshis by their position within a UTXO. When multiple inputs are merged into one output, all their satoshis land inside that single UTXO at different sat offsets. The 7 inscriptions are still there — each one sits at its respective offset within the 200,000 sat UTXO.

The tool shows it as a Whale Ordinal simply because the UTXO is ≥ 20,000 sats. The badge reflects the UTXO size, not the value of the inscriptions. The tool also previously showed only one inscription per UTXO — this has since been fixed and all inscriptions inside a merged UTXO are now shown, matching what ordinals.com displays.

What this means for you:

The 7 inscriptions are not lost. However, you can no longer spend the clean sats independently — they are all tangled together inside one UTXO. To separate them you would need to send each inscription individually to its own output using an ordinals-aware wallet such as Xverse or UniSat, which understands sat offsets and will not accidentally destroy them.

If the projects behind those 7 inscriptions are dead and worthless, you can simply use this tool to merge or send that entire UTXO and reclaim the 200,000 sats (minus fees), accepting that the inscriptions will be burned in the process.

The inscriptions travel with the satoshis — they are not destroyed, they simply move to whoever controls the new address.

Sending to a bc1q address you own: The 7 inscriptions now sit inside your bc1q wallet. A standard bc1q wallet is not ordinals-aware and will not display them, but according to ordinal theory they are still attached to those specific satoshis. Since the projects are dead and worthless this does not matter — you simply have spendable BTC.

Sending to an exchange: The exchange receives the BTC, credits your account with the full value, and has no idea there are inscriptions on those satoshis. You get your sats credited as plain BTC. The inscriptions become the exchange's problem — and exchanges do not care.

Because the inscriptions are worthless you can send that UTXO directly to a bc1q address or an exchange without any concern. You will receive the full sat value (minus the network fee) as spendable Bitcoin.

They keep travelling. Every time those satoshis are spent, the ordinals move to the new output according to ordinal theory's first-in-first-out rule. They never disappear — they just keep moving through the blockchain, permanently attached to those specific satoshis, completely invisible to anyone not actively looking for them.

In practice, once inscribed sats land on an exchange or get mixed into a regular wallet and spent as normal BTC, nobody tracks them any further. The inscription IDs still exist on ordinals.com, but the satoshis are effectively absorbed into the general Bitcoin supply. The inscriptions become lost — technically still alive on the blockchain, but practically gone forever.

For worthless inscriptions from dead projects, this is completely fine. Just spend the BTC normally.

An inscription only ever lives on the first satoshi of the UTXO — sat offset 0. The remaining 29,999+ satoshis are just padding sitting alongside it, locked in the same output. The inscription protocol does not care how large the UTXO is — it simply marks the first sat, and everything else is trapped there with it.

There are several common reasons why you end up with a large UTXO holding an inscription:

The extra satoshis cannot be spent without also moving the inscription. This tool flags these as Fat Ordinals (5,000–19,999 sats) or Whale Ordinals (20,000+ sats) so you know which UTXOs have significant BTC trapped inside them. The recommended approach is to send the inscription to a safe Ordinals wallet first, then reclaim the freed sats separately.

Sending an inscription preserves the UTXO as-is. Xverse simply moved the entire 30,000 sat UTXO to UniSat — the inscription is still on the first satoshi and all the excess sats are still trapped with it.

To actually free the excess sats you need a specific operation called a split — where the wallet constructs a transaction with two outputs:

Most wallets do not do this automatically when you hit Send — they just move the whole UTXO intact. You need to look for a dedicated split or extract feature:

It can — 546 sats is the dust limit and is technically the minimum allowed output size. The reason wallets rarely go that low is:

546 sats is fine for a worthless inscription. For a valuable one, using 600–1,000 sats gives a safer buffer. The inscription output size is a wallet design choice — the protocol only enforces the dust limit floor.

Yes. The options are:

Existing wallets: UniSat's UTXO Manager has an Extract/Split feature that lets you set a custom inscription output size (~546 sats) and returns the rest to you as change. Ordinals Wallet and Xverse have similar options when sending inscriptions.

This tool: Click any inscribed UTXO to open the inspector panel, then click ✂ Split. Enter the inscription destination (where the 546 sat inscription output goes) and the change address (where the excess sats are returned). The tool builds and signs a single transaction with three outputs: inscription, change, and service fee.

If the UTXO contains multiple inscriptions (from a previous merge), only the first inscription lands in the 546 sat output. The remaining inscriptions stay in the change output — you can then split that change UTXO again to separate the next inscription, and so on.

Bitcoin Stamps are NFTs on Bitcoin — similar to Ordinals, but stored differently. Where Ordinals embed data in witness data (which nodes can theoretically prune), Stamps embed data directly in transaction outputs. Those outputs are part of the UTXO set, which every full node must keep forever. Stamps claim to be truly permanent in a way Ordinals are not.

stampchain.io is the official Stamps explorer and indexer. It lets you look up collections, check ownership, and track SRC-20 token balances.

Why does this tool check for Stamps? A single UTXO can contain both an Ordinal and a Stamp at the same time. If you spend it as plain BTC without checking, you lose both. This tool queries stampchain.io during scanning so you know exactly what is inside each UTXO before you do anything with it.

After a Split or Split All, each inscription lands on its own 546-sat UTXO. That is the minimum amount Bitcoin allows as a valid output — just enough to hold the inscription without locking up more BTC than necessary.

The problem is that Bitcoin itself does not know or care about inscriptions. A regular wallet sees a 546-sat UTXO and treats it as small, cheap change — and may automatically include it in the next transaction you send. The moment those 546 sats are spent, whoever receives them becomes the new owner of the inscription. Not you.

The inscription itself is never destroyed. It stays on the blockchain forever. But ownership transfers the instant the sats move. So treat every 546-sat UTXO like a collectible — not like spending money.

546 sats is the dust limit for P2WPKH outputs. Bitcoin nodes reject transactions that create outputs below this threshold — they consider them unspendable "dust" that would clog the UTXO set.

The exact limit depends on the output type: 546 sats for P2WPKH (bc1q), 294 sats for P2TR (bc1p). In practice, 546 sats has become the standard inscription output size because it works across all wallet types and is universally recognised by Ordinals wallets and marketplaces.

This tool shows a red ⚠ Safe to Spend: No on any UTXO that contains an inscription, so you always know before you act.

The fee comes directly out of the UTXO you are sending — the recipient simply receives a little less than the full amount. You do not need a separate UTXO to cover costs.

Example — sending a 196,000-sat clean UTXO to a bc1q address at a medium fee rate:

Sending a 546-sat inscription UTXO is different. There is not enough value in the UTXO to also cover fees. In that case you have two options:

• Select a clean UTXO alongside the inscription — the tool uses the extra sats to pay the fee and returns change to your address.
• The recipient pays — on marketplaces the buyer typically covers the fee via a PSBT where they add their own input.

In practice, when sending an inscription to another wallet or a marketplace, always select the inscription UTXO together with a small clean UTXO so the tool has sats available to pay the network fee.