Your says sent. The explorer shows a and a count. The still shows the old balance. A confirmed LTC deposit can be perfectly real and still be waiting for the exchange to recognize it. The quickest way to locate the delay is to match the actual output to the deposit instructions, check the exchange’s confirmation threshold, then open the exchange’s deposit history.
Take Kraken’s published Litecoin requirement. A transparent transaction with one confirmation has made it into a block. Kraken currently asks for twelve for an LTC deposit, so eleven more blocks have to arrive before that threshold is reached. We measured that exact interval with archived observations from our own Litecoin Core . Across 828 measured block windows, the median was 30 min 15 sec and the 90th percentile was 41 min 15 sec. The study ends at the twelfth confirmation. The exchange’s account ledger has its own clock.
- Find your next step in the deposit checklist
- Walk through a real Litecoin TXID
- See our first-to-twelfth confirmation measurement
- Check thresholds, minimums and MWEB rules
- Prepare a support ticket with the right evidence
Find the last step you can verify
Keep the sender’s withdrawal detail, a trusted Litecoin explorer and your exchange’s deposit history open at the same time. Each answers a different question. The sender tells you what it tried to send. The explorer tells you what reached Litecoin. The exchange tells you how it treated the deposit.
| What you see | What to check next |
|---|---|
| The sender says completed and provides no blockchain TXID | Ask the sending platform for its on-chain transaction ID. An internal withdrawal reference can identify a request inside that platform. |
| The TXID lookup returns no result | Check the source network, the complete hash and the sending platform’s broadcast status. Cross-check using another current Litecoin explorer. For a private MWEB transfer, start with a compatible wallet. |
| The transaction is visible with zero confirmations | It has yet to reach the depth required for a confirmed deposit. The missing-payment walkthrough covers broadcast and confirmation checks. |
| The transaction is confirmed and the recipient output matches | Compare the confirmation count with the exchange’s current requirement for native LTC. Check the minimum against the actual recipient output. |
| The threshold is met and there is no deposit entry | Check account context, deposit address history, supported route and the exchange’s status page. If the gap persists under the exchange’s guidance, send the receiving exchange the TXID and matching output index. |
| A deposit entry exists and shows a hold or failure | Use the exchange’s instructions for that status. Include the displayed status and deposit reference in your support request. |
| The deposit shows credited or complete | Check the account and balance view that received it. An exchange can distinguish credited funds, funds available to trade and funds available to withdraw. |
Keep the original transfer record while you diagnose it. Sending a duplicate creates a second transaction and a second deposit to investigate. After confirmation, raising a fee or rebroadcasting the original bytes has no way to change the exchange’s private ledger. Our repeat-payment test shows how to tell a broadcast retry from a new payment.
Match the output the exchange should have received
- Start with the network. Check the sender’s network label against the exchange’s instructions for native Litecoin. A ticker label can also appear on a token or on another chain. Use the explorer for the actual chain selected by the sender.
- Use the supplied for this deposit. Compare the full destination with the exchange record you used when sending. If today’s deposit screen shows a different address, look for address history or ask support how the old address is treated. Case handling depends on the address format. Let the wallet or address tool validate it.
- Find that address under outputs. Inputs tell you what was spent. One transaction can have several outputs, including change and payments for other people. If the sender batches withdrawals, the can be shared across customers. The output index, often called
vout, identifies the exact output within a transparent transaction. - Read the output amount in LTC. Compare it to the receiving service’s stated deposit minimum and the amount you expected. If the sending service charged a fee out of the requested amount, the amount in its preview may differ from the amount at the destination. Read the final withdrawal record and the output together.
- Record the and observation time. Keep the confirmation count together with the time you looked. Records from different tips or lookup times can show different counts. For a discrepancy, compare the services’ reported heights and hashes.
If the destination differs, classify that mismatch before worrying about the clock. A confirmed output to a valid but different address is evidence of where the coins went. The receiving exchange can advise on routes and addresses it controls. For address formats and recovery limits, see the wrong-network and address guide.
A real public TXID you can check now
This ordinary transparent mainnet transaction is the example already used by our checker. We compared its details with a second public data source. Its exchange destination and account status are unknown. For the walkthrough, suppose the deposit instructions in your hands specify the full address in output 0.
TXID 5b298c11cd0d368fec70f9a492598604d0394f5f01d0c146de94c3213bd602f8. Open the live transaction lookup · Cross-check the public record at BlockCypher.
| Field | Observed value | How to use it |
|---|---|---|
| Containing block | 3,184,849 | At this height the included transaction had one confirmation on that chain. |
| Output 0 | 0.13910114 LTC to ltc1qcqz4pnt3wsnwvn4yknmtt6stw4wfa20hp2t3ey | Use this amount if the full destination matches your deposit instructions. |
| Output 1 | 0.26177251 LTC | A separate output. The record alone does not give us its owner or business purpose. |
| Sum of both outputs | 0.40087365 LTC | Useful for transaction accounting. The matching output is the one relevant to the hypothetical deposit. |
| On-chain transaction fee | 0.00000141 LTC | The difference between total inputs and outputs in this ordinary transparent transaction. The relevant output already shows its own final amount. |
The input was 0.40087506 LTC. The outputs add up to 0.40087365 LTC, leaving 141 as the . If you matched output 0 and expected 0.13910114 LTC, those values reconcile. A support ticket naming vout 0 and its exact amount is more useful than a ticket saying “the explorer shows 0.4 LTC.”
For an active chain tip at height T and an included transaction at height H, the count is T − H + 1. In this example the twelfth confirmation arrived when the active tip first reached 3,184,860 with the containing block still on that chain. The live lookup shows the count at the latest observed tip. A reorganization can change the count or remove an inclusion.
How long did it take from one to twelve confirmations?
The published Litecoin block target is 2 minutes 30 seconds. Eleven more blocks at exactly that spacing would take 27 minutes 30 seconds. It is a useful reference for the interval after the first confirmation. Individual blocks arrive irregularly, so the arithmetic gives no appointment time.
We replayed seven complete UTC days of archived polling from 13 through 19 November 2026. Each measured window starts at the poll when our Litecoin Core node first observed a block containing a sampled transaction. It ends at the poll recording the block eleven heights higher. We count a starting height once, even when it contains many sampled transactions.
| Statistic | Observed interval | How to read it |
|---|---|---|
| Shortest measured window | 11 min 30 sec | Fastest in this sample. |
| 10th percentile | 21 min 01 sec | About one in ten measured windows was this short or shorter. |
| Median | 30 min 15 sec | The midpoint of the measured windows. |
| 90th percentile | 41 min 15 sec | About one in ten measured windows took longer. |
| 95th percentile | 46 min 49 sec | About one in twenty measured windows took longer. |
| Longest measured window | 63 min 31 sec | Slowest in this sample. |
In this sample, 420 of 828 windows (50.7%) took longer than 30 minutes once the first confirmation had already arrived. 51 (6.2%) took longer than 45 minutes. The slowest observed window started at height 3,214,362 at 2026-11-16 at 23:17:35 UTC and reached twelve at height 3,214,373 at 2026-11-17 at 00:21:06 UTC.
If your deposit is at nine confirmations and the threshold is twelve, there are three more blocks to go. Multiplying three by the 2.5-minute target gives a reference of 7.5 minutes. The actual wait starts from wherever the chain is in its next-block cycle, and the deposit may still need exchange-side processing afterward. Our week-long sample is useful for calibrating patience. A receiving service’s live status and the actual chain ahead of your payment are better evidence for your particular case.
How we counted the windows
The daily ZIPs contain a poll log and a retained transaction cohort. We verified all seven archive hashes against the index and both CSV hashes against each ZIP manifest. Successive cohort snapshots repeat transactions, so we use the final snapshot alone, taken at 2026-11-20 at 00:03:11 UTC, to recover first observed blocks. The observer samples roughly one in sixteen eligible public TXIDs by prefix. A block enters the height map only when at least one of those sampled transactions is still labeled confirmed in that snapshot and its confirmation time matches a collecting poll.
The poll logs cover 99.15% of the scheduled seconds under the collector’s continuity rules. We identified 3,250 start heights and measured 828 windows, or 25.5% of the candidates. Of the 2,422 remaining windows, 9 fell beyond the last mapped height, 559 lacked an observed target, 1,226 crossed a polling gap, and 628 lacked an observed intermediate block. The filter also set aside 15 matched transaction rows whose recorded inclusion time lacked a collecting poll in the exported log. A short interruption can disqualify several overlapping windows. The high coverage by clock time therefore coexists with a much lower share of usable windows.
Each measured window requires an observed block at every height from H to H + 11 and an uninterrupted run of eligible polls between its two timestamps. The node nominally polls every 15 seconds. The times represent when this observer saw each endpoint, with poll cadence and block relay affecting the reading. Windows overlap and consecutive starts share blocks. The percentages describe these recorded windows. Observations without a complete window, blocks without a sampled transaction, waits before the first confirmation and exchange crediting delays fall outside those timing statistics. The public example above is from September and is separate from the November timing sample.
Download the measured and excluded windows (CSV) · Download the full results and source hashes (JSON) · Download the Python calculation · Get the archive index. To reproduce, download the November 13–19 ZIPs from the confirmation archive into the same directory as the index saved as archive-index.json. Run python measure.py.txt DOWNLOAD_DIR OUTPUT_DIR.
Where the exchange’s deposit rules come in
A confirmed output answers a question. The exchange still has to recognize the route and associate the output with an account, check its deposit rules and update the ledger. Platform terms and account screens can differ by country, product and date. Start with the authenticated deposit instructions for the exact account you are using.
Kraken’s published LTC rules
Checked 20 November 2026. Kraken’s public processing table lists 12 confirmations for Litecoin and an estimated 30 minutes. Its public minimum table lists 0.01 LTC. The authenticated deposit screen shows the current instructions for your account. Kraken says a deposit under the minimum fails and sending a separate qualifying deposit will not credit the earlier one. Its deposit documentation also says that transfers sent via Litecoin , including , will not be credited and may be lost. Kraken processing times and MWEB policy · Kraken deposit minimums.
| Status | What to check |
|---|---|
| Processing | The network confirmation phase is in progress. Compare the outpoint and depth. Check for maintenance if the platform displays stale information. |
| Credited | Where this stage is used, the funds are available to trade and withdrawals are still restricted. Some assets skip this stage. |
| Complete | Kraken describes this stage as available for trading and withdrawal. If your balance view disagrees, include the deposit entry and account context in your support request. |
| On hold | The support team has a manual review to perform. Use the official channel and include the deposit reference. |
Kraken’s deposit status definitions · Kraken service status.
What to check at Coinbase Exchange or another venue
Coinbase Exchange documents a per-asset confirmation requirement and provides an asset metadata lookup for its network_confirmations field. Its retail Coinbase help has a separate deposit and account workflow. Use the instructions for your receiving product. If the requirement is absent from a generic help page, read the deposit screen or ask support which threshold applies to that route. Coinbase Exchange deposit documentation · Coinbase pending transactions.
Three cases that can look like a slow block
- A minimum applied to the delivered amount. Suppose a deposit minimum is 0.01 LTC and a sender takes 0.0005 LTC from a 0.0100 LTC withdrawal. If the destination output is 0.0095 LTC, it falls short by 0.0005 LTC even with twelve confirmations. The numbers are illustrative. Once the transfer is confirmed, the amount to show support is the actual output value.
- An old exchange address or an unexpected account. An explorer can show coins going to a previously used address. The exchange determines whether that address still maps to your deposit account. Attach the historical instructions or old deposit reference if you have them, and verify which account or subaccount you are viewing.
- A route the receiving service excludes. A transparent output can be associated with an MWEB peg-out. A service can apply route restrictions even when the visible address looks familiar. Check the sender’s payment route and the receiver’s rules. A public explorer cannot reconstruct the private part of the transfer. Litecoin MWEB privacy and compatibility.
What to send to support after you check the output
Contact the sending service if the transfer lacks a usable public TXID. Contact the receiving exchange if the correct output has reached the applicable threshold but its deposit history remains blank, shows a hold or gives a failure you cannot reconcile. Keep the conversation inside the provider’s authenticated support channel. If a service asks for account documents, use its official case workflow.
| Field | What to fill in |
|---|---|
| Issue | Native Litecoin deposit confirmed on-chain and absent from my balance or on hold. |
| Transaction | Full TXID, matching vout, full deposit address and exact output amount in LTC. |
| Chain evidence | Containing block height, observed confirmation count, date and time with UTC offset, and explorer link. |
| Account evidence | Deposit status shown, deposit reference if one exists, relevant receiving account or subaccount and screenshot with unrelated details redacted. |
| Specific question | “Can you confirm whether this output was detected and which deposit condition or account check is still open?” |
The transaction checker can copy a source-stamped lookup summary. Add the exact recipient output and exchange reference yourself. A TXID is public on-chain information, but sharing it alongside your account details can connect you to that activity. Send it privately to the provider. Keep , , passwords and one-time login codes out of the ticket. See the payment support evidence guide for what each field proves.
Frequently asked questions
My explorer says confirmed. Has the deposit reached the exchange?
The explorer reports inclusion in a block. If the destination matches the exchange’s instructions, it also gives you evidence of the matching output and its value. The exchange alone can tell you whether it credited that output to your account.
Does twelve confirmations mean twelve blocks after my payment’s first block?
The containing block already counts as the first confirmation. Eleven more blocks on top of it bring the transaction to twelve. The applicable depth depends on the receiving service.
Why does one explorer show fewer confirmations than another?
Providers can capture different chain tips or serve cached results. Compare the block hash, the tip height and the lookup time before reading more into the discrepancy. A real branch change can also affect the count.
Can I add a second payment to make the first one pass the minimum?
For Kraken’s documented policy, a later qualifying payment will not credit an earlier below-minimum deposit. Check the receiving service’s exact rules before taking any action. A separate transfer creates a separate on-chain output.
What if the original deposit address has changed?
Find the address originally supplied for that deposit. The provider’s address history or support team can tell you whether it still maps to your account. An old address can remain valid on Litecoin while its exchange credit behavior depends on the provider.
Can the sender speed up an exchange credit once the transfer is confirmed?
For a confirmed output, the remaining wait is usually for more depth or for receiving-side processing. Collect the TXID and the exact output, then check the receiving exchange’s current status and instructions. A new payment adds another item to reconcile.
Start with the output, record the depth, then check the receiving exchange’s deposit history. Those three records tell you which party can answer the next question.
The cover is an AI-generated editorial illustration of a Litecoin token, observed blocks and a waiting vault.
