Before you send Litecoin again, check the original payment
An exact rebroadcast left one receipt in our isolated Core test; a new Send created a second. Find the original transaction and recipient output before retrying an uncertain payment.
AI-generated editorial illustration of a transfer path and a paused second route; it represents checking before retrying, not automatic cancellation or reversal.
On this page
Dotted-underlined terms open a quick definition. Close it to keep reading.
We sent 0.125 LTC to a disposable test , then submitted exactly the same signed transaction again. The recipient still had one 0.125 LTC receipt. We then created another payment to the same , for the same amount, with the same invoice comment. The recipient had two receipts, totaling 0.25 LTC.
That difference matters when a checkout spins, an withdrawal looks stuck or a payment notification never arrives. Repeating the delivery of an existing transaction and creating another payment are different operations. A button labeled “Retry” does not tell you which one an application will perform. Before using it, identify the original attempt.
This guide pairs a beginner workflow with an original, reproducible Core experiment. All measured amounts below are regtest coins from fresh disposable wallets, not mainnet payments or a test of a particular shop or exchange.
Before touching Send again, open the original payment
Start in the wallet or exchange that made the first attempt. Open its transaction or withdrawal history, rather than returning immediately to the checkout’s payment button. A shop’s unpaid label describes its own account state; it does not establish that no exists.
Record the original request. Keep the invoice or order ID, the agreed amount in LTC, the receiving address and any expiry time with its timezone. A new conversion is not a substitute for the amount on the original invoice.
Find the original attempt. Note its status and whether it has a blockchain transaction ID. An exchange withdrawal ID or a shop order number is a different identifier. Ask the sender’s service for the if it says a withdrawal was broadcast but does not show one.
Match the recipient output. For an ordinary transparent transaction, use its details and our transaction checker to compare the destination and the amount actually allocated to it. Record the output index if available. Do not count the sender’s change as another payment to the merchant.
Resolve that attempt before creating another. If the chain record and the shop’s status disagree, ask the shop to reconcile the existing transaction. If the withdrawal status is unclear, ask the sending service whether it created a transaction. Keep both questions attached to the original attempt.
No transaction found in one lookup is an incomplete observation, not a cancellation certificate. Check the network, the identifier and the source you queried. The pending-payment guide helps separate a wallet, relay, and receiving-service delay.
Our test separated an exact rebroadcast from a new payment
On 15 October 2026, we ran one fresh Litecoin Core 0.21.5.8 regtest with a new sender wallet and a new recipient wallet. Peer networking was disabled. We generated the test ourselves and checked that the node had zero peers at every recorded stage.
The first wallet operation sent exactly 0.12500000 LTC without subtracting the fee from the recipient’s amount. We saved its signed raw bytes and submitted those identical bytes while the transaction was still in the . We then generated a block and submitted the same bytes once more.
Only afterward did we run a second wallet Send operation with the same address, amount and comment, INV-LW-DUPLICATE-001. Another generated block confirmed it. This is a controlled comparison of two specific operations; we did not click a wallet’s Retry button or test an exchange’s withdrawal interface.
The operation matters more than a button’s name. This diagram explains the two paths; the recorded outcomes are below.
Each distinct payment in this run paid a measured of 0.00001410 LTC, or 1,410 . Those are configuration-specific test results, not a current recommended fee. The experiment does not estimate mainnet confirmation time, service crediting time or refund probability.
What changed—and what stayed exactly the same
Observed results from the isolated regtest experiment; receipt totals include unconfirmed outputs unless stated otherwise
Operation
Recipient outputs
Recipient total
Additional miner fee
Create first 0.125 LTC payment
1
0.12500000 LTC
0.00001410 LTC
Submit identical bytes while pending
Still 1
Still 0.12500000 LTC
0 LTC
Submit identical bytes after confirmation
Still 1
Still 0.12500000 LTC, confirmed
0 LTC
Create second 0.125 LTC payment
2
0.25000000 LTC
0.00001410 LTC
The pending rebroadcast returned the original transaction ID. The post-confirmation submission returned the actual RPC error -27, “Transaction already in block chain.” Neither action added a transaction to the confirmed ledger or created another recipient output. There was no second fee payment from either rebroadcast.
The new Send operation produced a different transaction ID and a separate recipient output. Once both payments were confirmed, the recipient’s total was 0.25000000 LTC and the two miner fees totaled 0.00002820 LTC. Repeating the local invoice comment did not stop the second Send. Our payment-note experiment checks which wallet could actually see such a note.
Recorded stages, not elapsed-time measurements. A mempool receipt and a receipt with at least one confirmation are shown separately; generated regtest blocks do not measure network speed.
Identify a receipt by its output, not its notification
A transaction ID identifies a transaction. A transaction may contain the intended recipient output and an output returning change to the sender. The useful identity for one transparent receipt is the network, the transaction ID and the output index, usually written txid:vout. Output numbering starts at zero.
Our first receipt was output 0 of transaction 533e679a43…ccfaebc. The second was output 1 of d3cd3c43e4…8375f5. The full IDs and raw transactions are in the downloads. These are generated regtest fixtures; a mainnet explorer will not show this experiment.
This also explains why two emails or two webhook deliveries do not establish two receipts. They may describe the same txid:vout. Conversely, matching address, amount and invoice text did not merge our two independently created outputs. Merchants should reconcile output identities with orders, as described in our merchant verification checklist.
Two different transaction IDs alone still need investigation: altered or conflicting transactions can be related. Our second payment spent the first payment’s sender change, not the recipient’s output. Both could confirm, and did. We tested an accidental double payment, not an attempt to spend the same output twice.
Four situations that make a second payment tempting
The following cases are fictional teaching examples. They are not observations of real shops, exchanges or support teams. Their purpose is to identify the missing evidence before money moves again.
Fictional retry situations: follow the existing attempt first
What you see
What you actually know
Next useful action
Avoid assuming
F01: the shop still says unpaid
Your transparent transaction has the intended output and one confirmation.
Ask the shop to match that transaction and output to the order.
A confirmation guarantees that shop’s acceptance or account credit.
F02: an exchange withdrawal has no txid
You have an exchange withdrawal ID and a pending status.
Use authenticated withdrawal history or support to establish broadcast status.
No displayed txid means no payment can later be sent.
F03: the invoice expires
An original transaction exists, but the invoice UI is expired.
Ask the receiver how that payment will be treated before using a new invoice.
Expiry canceled the transaction or authorizes a top-up.
F04: two sends already appear
The wallet shows two different transaction IDs.
Inspect both input and recipient-output sets; record each attempt separately.
Both are final independent receipts—or that a third payment will fix matters.
In F03, keep the original invoice amount and deadline. Do not replace them with a fresh quote and send the apparent difference automatically. The invoice-clock examples separate a deadline from broadcast, observation and confirmation times. Our refunds and underpayments guide explains what must be agreed with the receiver.
When to wait, and who can resolve the mismatch
Waiting is appropriate while a known transaction remains pending and you are checking the correct destination and the receiving service’s requirements. Waiting alone does not fix a wrong address, missing order association or a service’s exception policy. The next action depends on where the evidence stops.
Questions that advance the investigation without creating another payment
Evidence state
Useful question
Where to ask
No blockchain ID available
Was this withdrawal broadcast? What is its transaction ID, or its confirmed cancellation status?
The sending wallet’s records or the sending service’s authenticated support.
Transaction exists, unconfirmed
Does the intended recipient output match, and what status does the sender report?
The transaction details and the sender’s documented troubleshooting process.
Correct output confirmed, account uncredited
Can you reconcile this output to my invoice, and what requirement or exception remains?
The receiving shop or service.
Two independent payments were made
Which order received each payment, and how will the excess be handled?
The recipient, using both payment records.
Use the service’s official authenticated channel. Send the order ID privately, the correct network, the transaction ID and relevant output, the amount, and timestamps with their UTC offsets. A public transaction ID is not a , but publishing it exposes linked transaction history. Never provide a seed, private key or to establish whether a payment arrived.
A recipient may apply confirmation requirements, late-payment rules or a refund process. Our regtest result establishes none of those policies. An explorer can help inspect a public transaction; it cannot decide that an exchange should credit an account or that a merchant owes a particular refund.
Keep one small record for each attempt
You do not need a complicated portfolio tool. Keep a private row for the original attempt: invoice ID, network, amount, destination, creation time, sender status, transaction ID, recipient output index and the time you checked it. If a second attempt already exists, give it a separate row instead of overwriting the first transaction ID.
That preserves the distinction between “I clicked once,” “the service created a withdrawal,” “this transaction exists” and “the receiver credited this invoice.” These statements can become true at different times. Recording the source of each status makes a support conversation much more specific.
Download the blank payment ledger and printable retry checklist. Keep completed copies private. Neither template asks for wallet secrets. If both payments arrived, switch from retrying to reconciliation; our payment tools can help organize the transaction evidence.
Check our result without trusting a screenshot
The version 1 research package contains the raw transactions, RPC trace, seven-stage CSV, actual runtime help, source hashes and code. With Python 3.10 or later, run python verify.py.txt after extraction. It works offline and writes nothing to the package.
The verifier decodes the ordinary transparent transaction bytes, recomputes transaction IDs, reads the input prevouts and outputs, and derives the fees in integer litoshi. It checks the JSON against the CSV and the recorded RPC operations. The original experiment passed 38 assertions; the offline check also checks the recorded successful shutdown and directory-cleanup flags.
The fresh-test program is separate: reproduce.py.txt requires the pinned Core binaries and creates new wallets. A rerun will generate different keys, IDs and potentially different output order or fees. It is unnecessary for checking the frozen evidence. Neither program should be pointed at a real wallet; the experiment accepts no existing data directory.
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
In brief A service for trading currencies or assets, whose custodial account balance does not give you control of its private keys.
A platform or service for buying and selling cryptocurrencies against fiat currencies or other assets. Trading methods, custody, supported pairs and withdrawal rules vary by service. A balance on a custodial exchange is an account claim; it does not mean you control the wallet's private keys.
For example After buying LTC on a custodial exchange, you request a withdrawal if you want it sent to your own wallet.
Common mistake Assuming an account balance means you possess the private keys, or overlooking the selected withdrawal network.
In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.
A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.
For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.
Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.
In brief Recorded in accepted blockchain blocks, unlike account changes a service may make only in its own records.
Recorded in the blockchain's accepted blocks. For transparent Litecoin, many transaction details are publicly visible, but an exchange's internal account changes need not create an on-chain transaction. Blockchain records alone do not establish an owner's identity or why funds moved.
For example A confirmed ordinary LTC payment appears in Litecoin blocks; an exchange moving balances between its own customer accounts may not.
Common mistake Assuming every account activity creates a blockchain transaction or that every large transfer is a trade.
In brief Government-issued money such as EUR or USD, including cash and bank deposits, separate from a wallet's displayed LTC valuation.
Government-issued money such as USD, EUR or GBP, whose value does not depend on redemption for a fixed quantity of gold or another commodity. It can exist as cash or bank deposits. An LTC price displayed in a fiat currency is a valuation, not an extra cash balance.
For example USD, EUR and PLN are fiat currencies; an LTC/EUR quote expresses one coin's price in euros.
Common mistake Confusing the fiat value shown by a wallet with an extra cash balance held in that wallet.
In brief A transaction identifier for looking up outputs and confirmations, which alone does not prove that a payment arrived.
The identifier used to look up a transaction. For an ordinary transparent Litecoin transaction it is shown as a 64-character hexadecimal string. Use it to inspect the transaction's outputs and confirmations; the ID alone does not prove a payment is confirmed.
For example Copy the TXID from your wallet's payment details into a Litecoin explorer to check the recipient output and confirmation count.
Common mistake Sharing a seed phrase to trace a payment, or treating a screenshot or TXID alone as proof that the expected amount arrived.
In brief A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
In brief A participant running network software; a full node checks rules but need not keep all old block files.
A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.
For example A pruned full node checks the chain but later discards old block files to reduce disk use.
Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.
In brief A group of transactions linked to the previous block under the network's rules.
A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.
For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.
Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.
In brief One node's local collection of accepted but unconfirmed transactions, which may differ from other nodes' collections.
A node's local collection of unconfirmed transactions it currently accepts. Nodes can see, retain or remove different transactions, so there is no single global waiting room. Appearing in a mempool is not confirmation or a guarantee of later inclusion.
For example One explorer may see your unconfirmed transaction while another node has not received it or has already removed it.
Common mistake Assuming that absence from one mempool proves the payment was never broadcast or that a seen transaction must confirm.
In brief For ordinary transparent Litecoin transactions, the fee is total input value minus total output value, separate from a service withdrawal charge.
For an ordinary transparent Litecoin transaction, the network fee is the total input value minus all output values, including change. Wallets estimate it using transaction size and a fee rate, so sending more LTC does not automatically mean a higher fee. A service's withdrawal charge is a separate quote and may already cover network costs.
For example Fictional inputs total 1 LTC, while recipient and change outputs total 0.99999 LTC: the network fee is 0.00001 LTC.
Common mistake Confusing fee rate with total fee, leaving change out of output totals, or equating a service's withdrawal charge with the full network fee.
Compare: Network fee vs withdrawal fee
Transaction Fee
An ordinary transparent transaction's network fee is its total input value minus its total output value; transaction size and fee rate help determine the estimate.
Withdrawal Fee
A service sets its withdrawal charge under its own rules, and that charge can differ from the network fee on the transaction it broadcasts.
One example If a fictional service deducts a 0.001 LTC charge from a 1 LTC withdrawal, the recipient receives 0.999 LTC; these figures do not reveal the transaction's network fee.
Remember: Check the final account debit, recipient amount and minimum separately; add a network-fee estimate only if it is an additional charge, so the same cost is not counted twice.
In brief An informal name for 0.00000001 LTC, the smallest Litecoin unit, with 100,000,000 in one LTC.
An informal name for the smallest Litecoin unit: 0.00000001 LTC. One LTC contains 100,000,000 litoshis. Some software uses the inherited label satoshi, so always check which coin and unit a screen means.
For example 10,000 litoshis equal 0.0001 LTC; 1 litoshi equals 0.00000001 LTC.
Common mistake Confusing a fee quoted per virtual byte with that many litoshis for the whole transaction.
In brief Secret data a wallet uses to sign spending; one key may cover only part of a wallet and must never be shared.
Secret data used to authorize spending under the conditions attached to coins. In a simple single-key wallet, anyone with that key can spend the coins it controls. A wallet may manage many keys; never share them.
For example A wallet signs a spend using a private key; the recipient only needs your payment, not that secret key.
Common mistake Sharing a key with support or assuming one exported key necessarily backs up every address in a wallet.
Compare: Seed phrase vs private key
Seed Phrase
Recovery words used by many wallets to rebuild key material; the correct format, optional recovery passphrase and wallet settings still matter.
Private Key
A secret used to authorize spending under its key conditions; one exported private key is not necessarily a backup of every key a wallet uses.
One example A fictional simple HD wallet can derive several receiving keys from one recovery setup; exporting just one of those private keys does not preserve the others.
Remember: Identify the complete backup method for the original wallet, keep secret recovery material offline and never paste it into this website.
In brief Recovery material for a specific wallet and format, whose coverage depends on when and how the backup was made.
A recovery copy of the material needed for a particular wallet, such as its wallet file and required configuration. Coverage depends on the format and when it was made; later imported keys may require a fresh backup.
For example A Core wallet-file backup made before a separate key import can omit that imported key.
Common mistake Treating a receiving-address list as a spending backup, or assuming every wallet file can be restored by another application.
Downloadable data or code · Controlled wallet / regtest · Beginner selection.
Content review recorded: 2026-10-15. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
One fresh Core 0.21.5.8 regtest node with peer networking disabled and two disposable wallets. Identical-byte rebroadcast in mempool and after confirmation versus a new send with the same address, amount and comment. No wallet interface, exchange crediting, replacement, MWEB, reorganization or mainnet speed experiment.
All 38 live assertions passed. Identical-byte retries kept one receipt of 0.125 test LTC. A new send created a second receipt and 0.250 total; each distinct transaction had a measured fee of 0.00001410 test LTC.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.