Frequently Asked Questions
What is this?
This is a Bitcoin transaction explorer that lists all transactions that spend
at least one Taproot input using the script path. This type of input is
generally rare, as protocols built on Taproot should use the key path whenever
possible and only use the script path as a fallback mechanism.
Each listed transaction includes fields such as size and fee and a list of all
its inputs along with their revealed spending scripts. If a transaction also
has non-script path inputs, those are shown in gray.
I still don't get it.
In order to make sense of what you see here, you should understand how
transaction inputs and outputs, scripting and Taproot all work.
I've sent a script path spending transaction but I don't see it here!
Only confirmed transactions are currently shown. Wait until your transaction
is included in a block and try again.
Why build this? Aren't there enough explorers already?
When I built this, no publicly available blockchain explorers decoded Taproot
scripts. That has since changed, but this website also shows transaction data
that wouldn't make sense for a general-purpose explorer to display, and
because of its very narrow focus I expect it to remain useful for getting
insight into Taproot script usage.
Why does this website look a lot like miningpool.observer?
We both use Bootstrap with minimal custom CSS. That said, some design inspiration was still drawn.
Some texts (particularly transaction labels) were also simply copied over.
The transaction has a virtual size of over 100 kvB. Most nodes do not relay transactions this large.
The transaction does not pay any fees. It was likely prioritized by the mining pool that mined its corresponding block.
The transaction pays a fee of less than 1 sat/vB. Most nodes do not relay transactions with such a low feerate.
The transaction burns its entire input value on fees.
The transaction spends over a third of its input value on fees.
The transaction sends to an address that it also spends from. Address reuse is notoriously bad for privacy.
The transaction pays a fee of 1 sat/vB. This is the minimum feerate for most nodes to relay the transaction.
The transaction has an OP_RETURN output. OP_RETURN outputs embed arbitrary data into the blockchain.
The transaction signals explicit Replace-By-Fee replaceability.
The transaction is time-locked to only be valid after a certain absolute block height.
The transaction is time-locked to only be valid after a certain absolute timestamp.
The spending script contains an OP_SUCCESS opcode. This type of opcode should not be used before its meaning is defined since it makes the script unconditionally valid when encountered during parsing.
The spending script does not have any signature checks.
The witness stack includes an unused annex. The annex is a mechanism for future extensions and should not be used until its meaning is defined.
The previous output commits to an unspendable key path by using 0x0000...0001 as the internal key. Using a randomly generated internal key is a more private way of disabling key path spending.
The script embeds raw data into the blockchain as an Ordinals Inscription.
The spend does not include any Merkle branch steps. That means the previous output provably commits to just one script, the one that was revealed.