How to import one old Litecoin payment without rescanning the chain

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 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 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 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 Deleting older block files after validation to save disk space, which can limit later rescans of old transactions.

A full node's deletion of older block files after validating them to reduce disk use. It still checks consensus rules and keeps current chain state, but the deleted history is unavailable for an ordinary local rescan. A pruning target is not a budget for the entire application.

For example A node can validate today's chain while lacking the old blocks needed to rescan a payment from years ago.

Common mistake Assuming pruning skips validation, or that switching it off instantly restores deleted historical block data.

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 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 wallet view that can show addresses and activity from public information but cannot sign a payment on its own.

A wallet view built from public information that can recognize addresses and transactions without holding their private signing keys. It can show a balance or help prepare a payment, but spending needs the appropriate signer or cosigners through a supported workflow.

For example Importing an address or xpub can reproduce a receiving view while leaving that wallet unable to sign on its own.

Common mistake Treating matching addresses or a displayed balance as proof that recovery also restored spending authority.

In brief Submitting a signed transaction to a node for checking and sharing, without proving it has been confirmed.

Submitting a signed transaction to a node for validation and possible relay to peers. A signed file and its identifiers can exist before submission. Acceptance by one node does not establish that all peers saw it, a miner included it or a service credited it.

For example An offline signer can prepare a payment that remains outside the mempool until the approved transaction is submitted online.

Common mistake Treating a TXID or signed file as proof of broadcast, or treating a local submission response as a confirmation.

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.

In brief An unspent output from an earlier transaction, used whole when selected for an ordinary transparent payment.

An unspent transaction output: a recorded amount from an earlier transaction that has not been spent. A transparent Litecoin wallet can select eligible UTXOs as inputs for a new payment. Each selected output is spent in full; value left after the payment and fee can return as change.

For example Fictional receipts of 0.4 LTC and 0.6 LTC can be two UTXOs even when a wallet shows a single 1 LTC balance.

Common mistake Assuming the displayed wallet balance is one indivisible account entry, or that spending an input sends all of it to the recipient.

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 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 wallet's search of available blocks for matching transactions; blockchain data cannot replace missing recovery secrets.

A wallet's search through available blocks for transactions matching its keys or scripts. The scan needs the intended wallet configuration and readable history for the relevant period. It discovers transaction records; it cannot recover missing secret root material or an unrelated private key from blockchain data.

For example After importing the intended wallet material, a scan that covers the old receipt's block may discover that transaction.

Common mistake Scanning only recent retained blocks and assuming completion proves an old wallet's whole history was recovered.