To verify a Bitcoin payment, obtain its transaction ID (txid), look up the transaction in a blockchain explorer or your own Bitcoin Core node, and compare the recipient, amount, outputs and fee with what was intended. Then check whether a block contains it and count confirmations. A transaction that appears only in a mempool has zero confirmations and is not settled: a conflicting transaction could still be included instead. One confirmation establishes inclusion in the current best-chain tip, while additional blocks reduce reorganization risk. For high-value or fraud-sensitive payments, six confirmations is a commonly used conservative policy, not an absolute guarantee.
What transaction verification actually proves
A Bitcoin transaction is identified by a transaction ID, usually called a txid. The txid lets you retrieve the transaction record from a public blockchain explorer, a Bitcoin Core node, or an application using Bitcoin Core’s RPC or REST interfaces. Verification means checking the network record rather than trusting a screenshot, an email, or a wallet label.
As an Amazon Associate I earn from qualifying purchases.
The record should let you establish four separate facts:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- The transaction data matches the payment that was intended: the relevant sender and recipient addresses, the amount and units, and the outputs.
- The transaction is valid according to the node or service that accepted it.
- The transaction is either unconfirmed in a mempool or included in a particular block.
- If it is confirmed, its confirmation depth and position in the chain can be monitored.
These facts answer different questions. A valid transaction in a mempool has passed a node’s current validation and relay policy, but it has not yet become part of the block chain. A transaction in a block has one confirmation at the moment that block is the best-chain tip; each later block adds another confirmation.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Confirmation states and their operational meaning
| Status | What it proves | How to treat it |
|---|---|---|
| 0 confirmations (mempool only) | A node has accepted the transaction under its current validation and relay policy, but no block has included it. | Do not treat it as settled for irreversible delivery. A conflicting transaction can still win inclusion. |
| 1 confirmation | The transaction is in the current best-chain tip block. | Suitable for a low-value payment when the recipient accepts short-term reorganization risk; wait for more depth when loss would matter. |
| 2–5 confirmations | The transaction is buried under additional blocks. | Replacement risk is lower. Select a threshold according to the payment’s value and the plausible adversary. |
| 6 or more confirmations | The transaction has substantial chain depth. | A common conservative rule for high-value or fraud-sensitive payments, but not a universal guarantee. |
Step-by-step: verify a Bitcoin transaction
1. Copy the txid from the wallet
Open the sending or receiving wallet’s transaction details and copy the complete txid. A txid is a hexadecimal identifier; do not retype it. If the wallet offers a “copy transaction ID” control, use that and preserve every character. A wallet may show a local status such as “sent,” “pending,” or “complete,” but those labels are not proof of block inclusion.
If you are the recipient and the sender has not supplied a txid, request it. An address, a screenshot, or a claimed payment time is not enough to identify one specific transaction, especially when an address has received multiple payments.
2. Query the transaction in an independent record
Paste the txid into a reputable Bitcoin blockchain explorer, or query a Bitcoin Core node that you control. An explorer is convenient for a one-off check; your own node avoids disclosing the txid and related activity to a third-party service and gives you a local view of the chain and mempool.
Free tools Windows power users keep installed
One-click scans. No signup required.
Bitcoin Core supports both command-line RPC and REST access. The gettransaction RPC returns the txid and, when available, the amount, fee, confirmation count, block hash, block height, block index and block time. A REST request to /tx/<TX-HASH> can retrieve transaction data. For confirmed transactions, REST lookup may require starting Bitcoin Core with txindex=1; without that setting, the transaction endpoint searches the mempool by default.
For a wallet transaction, a typical RPC call is:
bitcoin-cli gettransaction "<TXID>"Replace the value in angle brackets with the actual txid. Read the returned confirmation field rather than inferring status from the wallet’s interface. A zero-confirmation wallet response can also include a trusted field; that field describes the wallet’s trust assessment and does not turn an unconfirmed transaction into a settled payment.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
3. Match the payment details
Compare the network record with the invoice or payment request before considering confirmation depth:
- Recipient: confirm that the intended recipient address appears in the transaction’s outputs. Check the entire address, not just its first or last characters.
- Amount and units: verify the exact bitcoin amount and whether the wallet or invoice expressed it in BTC or a smaller unit.
- Outputs: account for every relevant output. A transaction can contain a payment output and a change output returning funds to the sender.
- Fee: record the fee when the explorer or node provides it. The fee is part of the transaction’s economics, but it is separate from the amount delivered to the recipient.
- Transaction identity: ensure the txid in the record is exactly the one supplied by the wallet or sender.
If any address or amount differs, stop and resolve the discrepancy with the sender or your accounting system. Do not accept a screenshot as a substitute for the transaction record returned by a node or explorer.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →4. Decide whether it is unconfirmed or confirmed
A transaction shown only in a mempool has zero confirmations. Bitcoin Core defines a mempool as a set of transactions a node has verified as valid but that have not appeared in a block. Broadcasting a transaction proves only that it was sent to at least part of the network; it does not ensure that the receiver gets paid.
If the record contains a containing block hash and block height, it is confirmed. The block that first includes the transaction gives it one confirmation. The next block in the best chain raises the count to two, and so on. Do not count the transaction’s own block as zero: inclusion itself is the first confirmation.
5. Record the containing block
For an included transaction, save the block hash and block height returned by the node or explorer, along with the observed confirmation count and time. These values create an auditable reference for an invoice, withdrawal or release decision. The block hash identifies the exact block; the height identifies its position in the chain.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Use the block hash and height together when reconciling records. A height by itself can later refer to a different block if a short reorganization changes the chain at that position.
6. Refresh until your policy threshold is met
Refresh the transaction record or query your own node as new blocks arrive. A very recent block is the current tip and can be replaced during a short chain reorganization. Waiting for additional blocks increases the proof-of-work an attacker would need to replace that history.
If your node’s mempool no longer shows an unconfirmed transaction, do not conclude that it disappeared permanently. It may have been confirmed in a block that your node learned directly; block-learned transactions do not have to pass through your local mempool. Conversely, a transaction visible in one service’s mempool may be absent from another node because propagation, timing and relay policy differ.
What “finality” means on Bitcoin
Bitcoin does not mark a payment with an instant, mathematically irreversible finality flag. Settlement is probabilistic. Block inclusion sharply reduces the chance that the transaction will be replaced, and each subsequent block makes a replacement require more accumulated proof-of-work. The practical meaning of “final” is therefore a policy choice based on confirmation depth, transaction value and the threat model.
Bitcoin Core’s developer guidance describes six confirmations as a common threshold for high-value or fraud-sensitive payments. That guidance dates from 2015 and is a convention, not a network rule. A business can choose a different threshold if it documents why the payment’s value, delivery process and risk tolerance justify it.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Choosing a threshold by risk
- Low-value, reversible service: You may release the service at one confirmation if a short reorganization would be tolerable and you can recover from a failed payment.
- Moderate-value goods: Require more than one confirmation when shipping or providing access cannot be undone. Define the number in advance and apply it consistently.
- High-value or fraud-sensitive settlement: Six confirmations is a widely used conservative rule. Hold the goods or funds until the transaction reaches that depth, and retain the block reference in your records.
- Zero-confirmation acceptance: Treat it as an explicit risk decision, not as normal settlement. A conflicting transaction may still be mined, and a broadcast alone does not guarantee payment.
The statement that a transaction is “final” should include the rule that made it final, such as “six confirmations under our settlement policy.” Avoid presenting any confirmation count as an absolute guarantee against every possible chain event.
Verifying with your own Bitcoin Core node
When self-hosted verification is useful
A public explorer gives a fast, practical view but represents one service’s data and policies. A node lets you validate blocks and transactions locally, inspect your own mempool, automate checks and avoid sending txids or addresses to a third party. It is especially useful for exchanges, merchants, accounting systems and anyone who needs repeatable evidence rather than occasional manual lookups.
Bitcoin Core provides a graphical interface as well as command-line and API modes for viewing transactions, tracking payments, creating transactions and receiving block or transaction notifications. You can use the RPC interface for individual checks or build an internal process that records each transaction’s txid, confirmation count, block hash and block height.
Basic RPC check
- Ensure your Bitcoin Core node is running and accessible to the account or service that will perform the query.
- Run
bitcoin-cli gettransaction "<TXID>"for a transaction known to your wallet. - Read the returned txid and compare it with the txid you were given.
- Check
confirmations. Zero means the wallet has no confirmed inclusion; a positive value is the current depth. - When present, record
blockhash,blockheight,blockindexandblocktimewith the payment record. - Repeat the query as blocks arrive until your documented threshold is reached.
The wallet RPC is most straightforward for transactions associated with that wallet. For arbitrary transactions, use the REST transaction endpoint or a node configured with a transaction index so historical transactions can be located reliably.
REST and transaction-index considerations
Bitcoin Core’s REST interface includes /tx/<TX-HASH> and related block and mempool endpoints. Confirmed-transaction lookup may require txindex=1; with the default configuration, the transaction endpoint searches the mempool. Plan this setting before deploying an automated reconciliation service, because a node that cannot locate older arbitrary transactions cannot serve as a complete historical lookup without additional indexing.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Why a transaction is unconfirmed
It has not entered a block yet
The simplest explanation is that miners have not included the transaction. A mempool entry means the node considers it valid under current rules and relay policy, not that inclusion is guaranteed. Keep the txid and continue checking the confirmation count instead of treating “broadcast” as “paid.”
Different nodes show different mempools
Mempools are local. Propagation delays, connectivity, transaction-relay policy and timing mean two nodes can hold different unconfirmed sets. An explorer may show a transaction that your node has not received, while your node may show one that another service has not learned. This difference does not by itself prove that either record is fraudulent.
A conflicting transaction may win
Until a block includes the transaction, a conflicting transaction can still be selected for inclusion. This is why a recipient should not release an irreversible item solely because a txid appears in a mempool. If a conflict is reported, compare the outputs and wait for a confirmed transaction that pays the intended recipient.
The transaction is absent from your local mempool
Absence from one node’s mempool is not proof that the transaction failed. It may have expired from that node’s local pool, never reached it, or already been confirmed in a block learned directly from the network. Search the chain record and check the recipient output before asking the sender to rebroadcast.
Explorer lookup versus your own node
| Comparison | Public explorer | Your Bitcoin Core node |
|---|---|---|
| Independence | Relies on one service’s view and operating policies. | Uses the chain and validation performed by infrastructure you control. |
| Data scope | Usually presents indexed chain data and that service’s mempool view. | Provides your node’s local mempool and the full-chain data available to its configuration. |
| Privacy | Requires disclosing the txid, and potentially related addresses, to a third party. | Queries stay with your infrastructure unless you choose to expose the node or its API. |
| Automation | Convenient for manual checks; automation depends on the service’s interface and availability. | Supports RPC, REST integration and block or transaction notifications for repeatable workflows. |
| Finality policy | You must apply your own confirmation threshold to the displayed count. | You can enforce a threshold in software and store the block evidence internally. |
For a single personal payment, an explorer can be sufficient when you independently verify the txid and outputs. For recurring settlement or sensitive funds, querying your own node reduces dependence on a third-party presentation and makes the confirmation rule auditable.
Quick Recap
Common verification mistakes
- Confusing a wallet status with confirmation: “Sent” describes a wallet action. Use the txid record and confirmation count to establish inclusion.
- Accepting a screenshot: Screenshots can omit the txid, alter displayed units or show an unrelated transaction. Verify the live record.
- Counting the first block incorrectly: The containing block gives one confirmation, not zero.
- Assuming mempool presence is payment: A valid, relayed transaction can still be displaced before inclusion.
- Checking only a local mempool: A transaction confirmed elsewhere may never have appeared in your node’s mempool.
- Using height without the block hash: A short reorganization can replace the block at a height. Store both values.
- Treating six confirmations as universal law: Six is a common conservative policy for high-value or fraud-sensitive payments, not an absolute guarantee or protocol requirement.
- Failing to define “final” before accepting payment: Write the confirmation threshold and release action into the operating procedure so staff do not improvise under pressure.
A practical settlement checklist
- Copy the complete txid from the wallet or sender.
- Look it up in a reputable explorer or query your Bitcoin Core node.
- Match the intended recipient output, amount, units and fee when available.
- Record whether the transaction has zero confirmations or a containing block.
- If confirmed, save the block hash, height and current confirmation count.
- For a recent block, continue monitoring because the chain tip can reorganize.
- Apply the preselected risk policy: do not release irreversible value at zero confirmations, and use a higher threshold when the payment’s value or fraud exposure warrants it.
- Document the final confirmation count and the evidence used for the release decision.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
