Overview — what this page covers
If you've ever seen "status unconfirmed ledger wallet" or the message "ledger says send successful but coin not sent," this guide is for you. I write from hands-on testing with hardware wallets since the 2017–2018 cycle and from repairing dozens of stuck transactions for friends. What I've found is that the root cause is almost always one of two categories: the transaction was signed but not broadcast (a client/server problem), or the transaction was broadcast but stuck on-chain (fees, network, nonce).
I'll explain how signing differs from broadcasting, walk through the most common failure modes (including when you see a "ledger transaction rejected by server" message), and give a clear step-by-step troubleshooting checklist you can follow right now.
How signing and broadcasting work (why the wallet can "say" success)
A hardware wallet holds your private keys and signs transactions inside its secure element. The host app (desktop/mobile wallet) then builds a signed transaction and asks a node or service to broadcast it to the blockchain. Two distinct steps. Two failure points.
- Signing: done on the hardware wallet, typically confirmed on-screen by you.
- Broadcasting: done by the desktop/mobile app or a remote server. This is where you often see the mismatch — the device confirmed the signature, but the broadcast failed.
So when people report "ledger says send successful but coin not sent," they usually mean the device signed the transaction successfully but the host's broadcast step failed or the node rejected the transaction ("ledger wallet transaction rejected by the server").
Common blockchain reasons for unconfirmed or missing transfers
- Low fees: If the fee was too low for the moment, miners/validators may leave the transaction in the mempool for hours or days.
- Network congestion: High traffic spikes (e.g., NFT mints, token launches) push fees up and leave lower-fee transactions unconfirmed.
- Wrong chain or token: Sending an ERC-20 token on a different network or using the wrong address format can make the transfer appear missing.
- Nonce conflicts: For Ethereum-like chains, an incorrect nonce can cause broadcasts to be rejected.
Short sentence. Wait a few minutes. I often see low-fee transactions confirm after hours when congestion eases.
Device and wallet causes (server rejections and syncing issues)
- Server-side rejection: Some wallet apps rely on remote nodes or indexing servers. If those servers see a malformed transaction, a duplicate, or an out-of-sync nonce, they'll reject it and report an error such as "ledger transaction rejected by server."
- Local client out-of-date: If your desktop/mobile wallet or the companion app isn't synced or is outdated, it may misreport statuses ("ledger wallet your wallet may not be up-to-date").
- Connectivity: Bluetooth/USB/NFC problems can interrupt the signing/broadcast pipeline (see our guide on bluetooth-usb-nfc-security).
- Hidden accounts / passphrase mismatch: Using the wrong passphrase or derivation path makes funds appear missing even though the transaction actually happened on-chain for another hidden account.
And sometimes the simplest thing is the right thing: reconnect, reopen the app, and check again.
Quick symptom → cause → fix table
| Symptom |
Likely cause |
Quick action |
| No TXID shown after sending |
Transaction never broadcast |
Reopen app; check connection; try again (do not re-enter seed phrase on unknown sites) |
| TXID exists but unconfirmed |
Low fee / network congestion |
Check explorer; wait or speed up with replace-by-fee if supported |
| Error: "rejected by server" |
Node/indexer rejected tx (nonce, malformed) |
Reconnect to different node or rebroadcast via another wallet/node |
| Funds not visible |
Wrong passphrase / account |
Unlock with correct passphrase or check derivation path |
How to troubleshoot: step-by-step (How to / Step by step)
Find the transaction ID (TXID). Open your wallet app and look in transaction history. If the app shows "send successful" but no TXID, the transaction likely never left your host.
Check a blockchain explorer. Paste the TXID into a reputable explorer for the chain (Bitcoin, Ethereum, Solana, etc.). Does the explorer show the TX as unconfirmed, confirmed, or not found? This isolates client vs on-chain problems.
If the TX exists but is unconfirmed: check the fee. For Ethereum, look at gas price; for Bitcoin, check sat/vByte. If fee is low, you can attempt a replace-by-fee (RBF) or "speed up" through your wallet — only if your wallet supports it.
If the server rejected the transaction (you see messages like "ledger wallet transaction rejected by the server") try switching the broadcasting node: reconnect the hardware wallet to another host, or use a different wallet app that supports the same hardware wallet. (This avoids re-entering your recovery phrase.)
If the TX is not on-chain at all: the signed transaction may be stuck locally. Reopen the sending app, reconnect the hardware wallet making sure the correct app and account are selected, and attempt to re-send. If you used a passphrase originally, unlock that same passphrase first.
Advanced: If you can export the raw signed transaction (some apps allow this) you can rebroadcast through an alternate node or broadcast tool. Be careful — only broadcast signed hex; never expose your private keys or seed phrase.
If nothing helps: document the TXID, firmware version, wallet/app version, and the exact error messages. Those details matter if you seek help.
Is it okay to close a Ledger Nano S with an unconfirmed transaction?
Many search queries look like this: "ledger nano s okaay to close wallet with unconfirmed transaction" — short answer: usually yes, but with caveats. Closing or disconnecting the hardware wallet after the device has signed a transaction does not halt an already-broadcast transaction. But if the host app hadn't yet broadcast or crashed during broadcast, closing the device may leave the host in a bad state and the transaction may not have left your machine.
If you want to be conservative, wait until you see a TXID and then check a block explorer. If you only saw on-device confirmation and no TXID, reopen the app to confirm broadcast. But don't panic; closing the device doesn't burn your keys or your seed phrase.
Passphrase (25th word) and account indexing: missing funds explained
Using a passphrase (sometimes called a 25th word) creates hidden accounts. If you send from a hidden account while later unlocking the non-passphrase account, the transfer will be invisible to you even though it succeeded on-chain. I once helped a friend who reported a missing transfer — it turned out they were looking at the wrong hidden account.
If you think this is the issue, review our passphrase-25th-word-guide and the restore-recovery-phrase walkthrough before attempting any restores.
Preventive practices and when to ask for help
- Keep firmware current and verify authenticity before updating (see firmware-update-guide).
- Use trusted nodes or run your own node if you broadcast large transactions frequently (this avoids remote server rejections).
- For large balances, consider a multi-signature setup (multisig-for-ledger).
- Always confirm the address and network before sending.
If you still need help, gather TXID, timestamps, firmware and app versions, the device model, and screenshots of the error messages. Then consult our troubleshooting-general and troubleshooting-apps pages. But if you prefer direct support, official channels can process logs more efficiently when you provide the details above.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes — your crypto is controlled by your recovery phrase and private keys. See restore-recovery-phrase for steps.
Q: What happens if the company behind the wallet goes bankrupt?
A: Because hardware wallets are non-custodial, your private keys and funds are still yours. Company bankruptcy can affect companion services and updates, though — read company-bankruptcy-what-happens.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth adds convenience and additional attack surface. I use Bluetooth for small, everyday transactions and USB for large or sensitive moves. See bluetooth-usb-nfc-security for details.
Q: What if I see "ledger wallet send syncing" or the app says "your wallet may not be up-to-date"?
A: That usually indicates a client-server sync issue. Update the app, reconnect, and check again. See ledger-live-guide and firmware-update-guide.
Final notes
Transaction troubles are usually fixable with patience and the right checks: find the TXID, confirm on-chain, verify passphrase/account, and if needed rebroadcast via another node. I believe a calm, step-by-step approach keeps coins safe and avoids rash decisions (like exposing a recovery phrase). But if you want guided, model-specific instructions, try the step-by-step setup and troubleshooting pages linked below.
If you need more detailed walkthroughs, start with: setup-ledger-step-by-step, firmware-update-guide, and passphrase-25th-word-guide.
If this guide didn't resolve the issue, see troubleshooting-general and troubleshooting-connection for deeper diagnostics.
