Technical
Reading a Transaction: txid, Confirmations, Explorer Link
This module involves looking up a txid in the lab, then interpreting the resulting JSON from the perspectives of input, output, confirmations, and explorer link.
Transactions are looked up by an identifier called a txid. The values shown by explorers or APIs are more detailed than a wallet screen, but it can be hard to know which fields are important at first glance.
In this lesson, we recommend first checking the confirmation count and status, then the inputs and outputs, and finally the explorer link and raw JSON.
Plain words
First-time terms
- txid
- A long number used to find a single transaction.
- Confirmations
- A number that shows how much more secure a transaction is after being included in a block.
- Explorer
- A tool to search the public ledger on the web.
Learning objectives
- First check the status and confirmation count in the txid lookup result.
- Read the transaction flow by separating inputs and outputs.
- Understand that lookup functions are read-only.
Check Status First
The tx lookup in the lab sends the user-entered txid to a server-side API and shows the network lookup result as JSON.
Transactions with insufficient confirmations may change status later, so it is safer to first read the current lookup status rather than assuming finality.
An Order That Doesn’t Fear JSON
First find the txid and status, then look at the vin or input list and the vout or output list. Finally, open the explorer link to confirm the same values are visible externally.
Long hashes and addresses should be shown in line-breakable code blocks so the layout does not break on mobile screens.
Extending Transaction Reading to Payment Verification
Reading a transaction does not end with just looking at inputs, outputs, fees, and confirmations. It should extend to verifying actual events on the ledger like sponsorships, airdrops, Consol payments, and migration results.
Items to collect include txid, input UTXOs, output addresses, amounts, block height, confirmation time, and related announcements. Payment events gain verification strength when announcement text and actual transactions are stored together.
The next supplement will include examples of cases where the same amount is split into multiple outputs, cases with change outputs, and repeated transactions for events with payment cycles.
Read the Transaction Screen in Order
When opening a txid screen, first check the confirmation status, then the inputs and outputs. Following this order helps calmly track where the transaction came from and where it went.
An explorer is not a wallet and can only be used for lookup. Without this distinction, one might mistakenly think they can move coins from the public ledger screen or conversely feel unsafe just doing lookups.
Memory Points
Points to remember
Read Transactions in the Order: Status, Inputs, Outputs
When opening a txid, first check whether the transaction is confirmed and how many blocks have been added after it.
Next, look at the inputs. Inputs show which UTXOs this transaction used.
Finally, look at the outputs. The receiving address, change address, and fees are revealed here.
Explorer Is a Window, Not a Wallet
An explorer is a window to look into the public ledger. You can enter addresses or txids to read records, but it does not move coins.
A wallet is a tool that signs and sends transactions with user approval. Even if it shows the same address, the permissions of an explorer and a wallet differ.
Knowing this difference helps beginners reduce unnecessary anxiety on lookup screens and handle actual sending only inside wallets.
Practice
Look Up a txid in the Lab
- Open the lab page.
- Enter the txid you want to check.
- In the response, find the fields corresponding to txid, status, input, and output in order.
The learner can read the same transaction by comparing the explorer screen and the site’s read-only lookup result.
Create a txid Reading Order Card
- Write confirmation status, inputs, outputs, and fees on four cards.
- Arrange them in the order to check when viewing a transaction screen.
- Write below the cards why an explorer is not a wallet.
The learner can guide others on the order of items to check first on a transaction screen.
Key takeaways
- txid lookup is a starting point to read transactions, not a wallet permission request.
- Viewing in the order of status, inputs, outputs, and external explorer comparison reduces beginner burden.
- Long identifiers require UX that supports line breaks and copying on mobile.
- Reading transactions in the order of confirmation status, inputs, outputs, and fees makes it easier.
Quiz
Quiz
What should you look at first when viewing a transaction?
What does read-only lookup mean?
What is needed when showing long txids or addresses?
Evidence and statusSources connected
This localized lesson keeps the same source IDs as the Korean curriculum. Use the source library for ledger checks and official references.
- claim-electrum-readonly
- claim-education-style