Dotted-underlined terms open a quick definition. Close it to keep reading.
We sent 1 LTC to a new in the same Core test . Core reported a send for −1 LTC and a receive for +1 LTC. Both entries pointed to output 1 of the same transaction. The wallet kept the value it sent to itself and paid one of 0.00022200 LTC.
If your own history looks like this, start by checking the and output number. Then check who controls the destination and account for the fee once. A pair of rows by itself gives you less information than those checks.
Read the transaction and its details separately
In the recorded regtest RPC trace, the wallet named maker created the payment to an address it had just generated. After the transaction confirmed, its gettransaction response contained the following values. The amounts are in LTC.
The two detail rows have the same vout. The decoded transaction has a single 1 LTC output at that position. Output 0 is the 48.99977800 LTC . Core’s wallet code can list a non-change output among outgoing entries when the wallet funds a transaction and among incoming entries when that same wallet recognizes the destination. This is why both rows can describe the same output. Core wallet output classification.
The top-level amount and fee are separate. In this case the principal legs cancel, so amount is zero. The effect of this transaction on the wallet’s owned value is the fee, or −0.00022200 LTC. The fee shown beside the send row is the same fee as at the top level. Core’s detail code attaches the transaction fee to each send entry, so summing those fields can also count a fee more than once in transactions with several outgoing rows. Core send-entry fields and wallet transaction summary.
A read-only check in your wallet
Run this against your Litecoin Core with the relevant wallet loaded. Replace WALLET and TXID with your wallet name and transaction ID.
Match the output. Find the send and receive entries in details. A shared TXID can contain several outputs. A shared TXID and vout refer to the same transparent output on the same network.
Confirm the destination is yours. Compare it with the address from your own receiving wallet or a trusted transfer record. A shows the output and its value. Ownership comes from wallet and account evidence.
Reconcile the principal and fee. Keep the source rows so you can trace the record. If both sides belong inside your reporting boundary, record the transfer as internal and keep the network fee once. When the sender and receiver are separate wallets, reconcile each wallet against its own records before combining them.
In our trace the separate, uninvolved observer wallet returned error −5 for the same TXID, even though the transaction was confirmed. A wallet lookup describes what that wallet knows. The block lookup guide shows how the same transaction was retrieved at the node level. For transfers across several accounts, see the portfolio reconciliation guide.
Where the numbers came from
This is a second reading of one transparent transaction from our November 6 isolated Litecoin Core 0.21.5.8 regtest run. The byte strings in the wallet and node responses match. We recomputed the TXID and compared the decoded output with both wallet rows. The original runner documents the setup. Its fallback fee setting makes the observed amount a test result rather than a current mainnet quote. Other wallets and services can display a self-transfer differently.
Sources checked November 8, 2026. Research and drafting used AI assistance. The cover is a conceptual illustration.
Address
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 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 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 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 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 wallet-controlled destination for leftover LTC after spending an input on a payment and its fee.
Spending a transparent transaction output uses its whole value. After paying the recipient and fee, a wallet can send the leftover LTC to an address it controls. That destination is a change address. Wallets usually choose it automatically.
For example A fictional 1 LTC input paying 0.3 LTC with a 0.00001 LTC fee can return 0.69999 LTC to a wallet-controlled change output.
Common mistake Assuming an unfamiliar second output is a second payment to the recipient; first check which outputs your wallet owns.
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 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 tool showing its indexed view of public blockchain data, which cannot reveal a service's internal account status.
A website or app that indexes blockchain data so you can inspect blocks, transactions and outputs. It reports its own data view. Looking up a public transaction needs no private key, and an explorer cannot see a service's internal account-crediting decisions.
For example Look up a transparent Litecoin TXID to check the destination output, amount and reported confirmations.
Common mistake Entering recovery words to track a public transaction, or treating one explorer's missing result as proof that no payment exists.
In brief Who controls spending access; with a custodial service, the provider controls the keys behind your account.
Who controls the signing material and the process for moving funds. With a custodial service, the provider controls the relevant keys and you use an account. Self-custody places key and backup responsibility with you; an account password is not a private key.
For example An exchange withdrawal moves funds from the provider's control to an address whose signing keys your own wallet controls.
Common mistake Assuming an exchange balance and a self-custody wallet offer the same control, recovery process or withdrawal availability.
Content review recorded: 2026-11-08. 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.
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.
