Know what an explorer is showing
An explorer reads blocks, transactions and often a local mempool, then turns that data into searchable pages. You can usually search by transaction ID, block hash, block height, address or output reference.
The page is not part of Bitcoin consensus. Labels such as sender, recipient, exchange or miner are added interpretations and may be incomplete or wrong. Nodes decide validity by applying rules, not by consulting an explorer.
Read a transaction from inputs to outputs
Start with its status: unconfirmed, confirmed, replaced or conflicting. Then inspect the inputs it spends, the new outputs it creates, total input and output value, fee, virtual size and fee rate.
A wallet may know which output is payment and which is change. A public explorer normally infers this from patterns. Treat change labels as clues rather than proof, and remember that the fee is the input total minus the output total.
Separate a block's identity from its height
A block height is a position, while a block hash identifies one exact header. During a chain reorganisation, the block occupying a recent height can change, so systems that track confirmations should record hashes as well as heights.
A block page may show its parent, timestamp, weight, transaction count and coinbase transaction. Pool attribution is usually inferred from coinbase tags or known payout patterns; it is not a consensus field proving who controlled the hashpower.
Understand mempool and confirmation differences
Two explorers can disagree about an unconfirmed transaction because mempools are local. Relay timing, replacement rules, minimum fee settings and provider outages can produce different views without a blockchain split.
For confirmed data, first check whether the service is synchronized and which chain it follows. A recent transaction can lose confirmations during a reorganisation, while deeper history is progressively harder to replace.
Use explorers without giving away more than necessary
Searching an address tells the provider that someone at your IP address is interested in it. Repeated searches can link multiple addresses or transactions. Tor can reduce direct network linkage, but it does not turn the provider's results into independent verification.
Use an explorer for orientation, compare important claims with your wallet and, when possible, query your own synchronized node. Never paste seed words, private keys, wallet backups or unsigned spending policies into an explorer.
Visual recap
From explorer page to verified conclusion
Inspection helps you form a question; your own validation source should anchor important conclusions.
Search public identifier
Check status
Inspect inputs and outputs
Check block hash
Compare another source
Verify with your node
Key vocabulary
Terms worth knowing
- Transaction identifier
- A hash-based identifier used to refer to a transaction; for SegWit transactions, the txid excludes witness data.
- Block height
- A block's position in a chain measured from the genesis block, not a unique identity by itself.
- Local mempool
- One node's current set of accepted unconfirmed transactions, which may differ from another node's set.
Worked example
The explorer and your node disagree
A public explorer labels a payment confirmed, but your fully synced node does not show that transaction in its active chain.
- 1Confirm your node is synced
- 2Compare the exact txid
- 3Compare block hash as well as height
- 4Check whether a recent reorganisation occurred
- 5Use a second viewer only as supporting evidence
An explorer is a convenient index. Your validating node is the stronger authority for the chain and transaction state it has independently checked.
Common misconceptions
What learners often get wrong
Misconception
Every explorer sees one global mempool.
More accurate
Mempools are local and policy-dependent, so an unconfirmed transaction can appear on one node and not another.
Misconception
A block height uniquely identifies a block forever.
More accurate
Competing blocks can exist at the same height; use the block hash to identify one exact block.
Try it yourself
Inspect one public transaction without treating the explorer as a wallet.
- Record its txid
- List input and output counts
- Calculate or confirm the fee
- Open its containing block
- Compare the result with your node or another independent source
Use fictional values and public information only. Never enter seed words, private keys or other wallet secrets into a learning exercise.
Key takeaways
- An explorer is a searchable index, not a Bitcoin consensus authority.
- Transaction fees are derived from input value minus output value.
- Change and entity labels are usually heuristics rather than protocol facts.
- Recent block heights can point to different hashes after a reorganisation.
- Address searches can reveal your interests to the explorer provider.
Lesson recap
Check what you learned
Reveal each model answer, then honestly mark whether you understood it or need another review.
1 of 3
Recall
Two explorers disagree about whether an unconfirmed transaction is in the mempool. Does that prove Bitcoin has split?
References
