Bitcoin transaction not found: what to check
A missing result is not proof that a payment failed. Check the ID, network and sending wallet before sending again.
1. Check the ID and network
Copy the full transaction ID from the sending wallet’s payment details. An exchange order number is not a Bitcoin transaction ID. A Lightning payment hash can look similar, but this explorer cannot look up an individual Lightning payment. Confirm that the sender used Bitcoin’s main network, not Lightning or a test network.
Check a payment sent on the wrong network2. Ask whether it reached the network
A withdrawal can be queued inside a service before it is broadcast. Ask the sender for the transaction ID and its current status in their app. A screenshot marked “sent” does not establish that our data provider has seen a Bitcoin transaction. If the sender has a replacement ID, use that instead.
3. Separate a missing result from a data problem
If UTXOHub reports that the data is unavailable, try again later. A missing result means our provider did not return that transaction; it is not a verdict about your funds. Check the sending wallet’s own status and whether it has a supported replacement or fee-bump option.
Why disappearance is not cancellation
Each node keeps its own mempool and can remove an unconfirmed transaction, including when its mempool is full or its retention period ends. Another node may keep it, and the sending wallet or service may broadcast it again. It can still confirm unless a conflicting replacement has confirmed. Do not make a second independent payment merely because the first disappeared: both could confirm. Check the sending wallet or service and use its supported replacement flow, if available; the original may confirm first.
References
- Lightning Labs, “Payment Channels”.
- Bitcoin Developer Examples, “Testing Applications”.
- Bitcoin Core, “Opt-in RBF FAQ”.
- Bitcoin Core, “Bitcoin Core 28.0 Release Notes”.
- Electrum, “Frequently Asked Questions”.