Dotted-underlined terms open a quick definition. Close it to keep reading.
Research checked 22 September 2026. Methods and reproducible files are documented below. The hero is an AI-generated editorial illustration.
You have 5.229 LTC on an , 4.2498 LTC in a spending and 1.2499 LTC in . Your spreadsheet says 12.7287 LTC. Searching for a missing will not help: in the example below, the spreadsheet imported the same 2 LTC purchase twice.
The useful starting point is a quantity ledger. Reconstruct the coins first, separately for each account. Only then calculate their value, cost or investment return. A dollar discrepancy can come from a different quote; an LTC discrepancy needs an explanation in the transaction history.
Define the accounts and the cutoff
Write down every account you intend to include: exchange spot account, exchange funding account, each wallet, and any separate business holdings. A transfer between two included accounts stays inside the portfolio. A transfer to someone else's wallet leaves it. An account excluded from the calculation is outside the boundary even if you also own it.
Choose one cutoff, such as 7 September 2026 at 23:59:59 UTC. Record balances at that instant, not whatever an app shows while you import a week-old export. Note whether each balance includes unconfirmed receipts, pending withdrawals, locked orders or collateral. For a first reconciliation, use settled holdings and list pending items separately.
Export the complete ledger, deposits, withdrawals and trade executions. Keep the original files unchanged. A trade history alone may omit transfers and other balance changes. Kraken's documentation, for example, distinguishes trade records from per-asset ledger entries and explains that the ledger records the currency in which a fee was actually deducted. That distinction is useful even when your exchange uses different field names. Kraken: ledger versus trade history.
A ten-row ledger you can reproduce
Our example starts with zero LTC in all three accounts. It contains two buys, one sale, a 0.25 LTC receipt labeled “reward,” and three transfers. The reward is a generic external receipt, not a claim that offers protocol . All amounts and dates are synthetic. The exercise isolates quantities; USD charges on the final buy and the sale belong in a separate cash ledger and do not reduce LTC.
In this normalized CSV, amount is signed principal and fee is a positive deduction in the same asset. Therefore balance change = amount − fee. This is our file convention. Check a provider's convention before applying it to an export whose amount may already include the fee.
Synthetic LTC ledger; fee is deducted separately
Row / date (2026)
Account / event
Principal LTC
Fee LTC
Transfer
L01 / 09-01
exchange / buy
10
.02
—
L02 / 09-02
exchange / transfer_out
-6
.001
T01
L03 / 09-02
hot / transfer_in
6
0
T01
L04 / 09-03
hot / transfer_out
-2
.0002
T02
L05 / 09-03
cold / transfer_in
2
0
T02
L06 / 09-04
exchange / sell
-1.5
0
—
L07 / 09-05
hot / reward
.25
0
—
L08 / 09-06
cold / transfer_out
-.75
.0001
T03
L09 / 09-06
exchange / transfer_in
.75
0
T03
L10 / 09-07
exchange / buy
2
0
—
The exchange sends exactly 6 LTC to the and debits an additional 0.001 LTC. Later, the hot wallet sends exactly 2 LTC to cold storage and pays 0.0002 LTC. The cold wallet sends 0.75 LTC back to the exchange and pays 0.0001 LTC. The recipient credits and the transfer principals cancel across the portfolio; the three fees do not.
Original calculation; account totals are independently reconciled in the table below. Download full-size SVG. Scroll the figure horizontally on a narrow screen.
That total is a useful control, but it is not enough. An omitted receipt in one wallet and a duplicated receipt in another can cancel in the total. Require all three account balances to match as well.
Match transfers without inventing a buy or sale
Use the exchange withdrawal reference, , destination and amount together. A transaction ID is not always a unique payment identifier: a batched exchange transaction can pay many customers. For a transparent on-chain receipt, the output index identifies the specific output. A provider's internal transfer may have no blockchain transaction at all.
For each transfer, preserve two ledger rows and assign a shared transfer ID. Do not delete both rows merely because their principals cancel. They are needed to reconcile individual accounts and to identify the fee. In the fixture, T01 connects L02 and L03, T02 connects L04 and L05, and T03 connects L08 and L09.
A wallet transaction's total input amount is not necessarily the amount sent to another person. Change can return to a new address in the same wallet. Reading every output as a withdrawal will overstate spending. Use the wallet's transaction accounting and consult our guide to UTXOs, change and coin control when the explorer view differs from the wallet view.
MWEB transfers need the wallet's records and the exchange's deposit or withdrawal records where applicable; do not assume a public explorer exposes all amounts or ownership relationships. Mark an unmatched leg as unresolved and retain the evidence. Do not create a zero-cost purchase just to make a balance turn green.
Six import errors and the residual each leaves
We applied each error independently to the correct ten-row fixture, then recomputed all balances with decimal arithmetic. A positive residual means the imported ledger claims more LTC than the correct balance. These are controlled fault injections, not a survey of exchange reliability or estimates of how often errors occur.
Six independent faults applied to the same correct ledger
Injected fault
Imported total LTC
Residual LTC
Omit LTC purchase fee
10.7487
0.0200
Omit all transfer fees
10.73
0.0013
Drop cold-wallet receipt
8.7287
-2.0000
Duplicate final buy
12.7287
2.0000
Subtract withdrawal fee twice
10.7277
-0.0010
Omit reward at export boundary
10.4787
-0.2500
The shape of the difference suggests where to look. A residual equal to a familiar trade size points toward a duplicate or missing execution. A small residual matching accumulated fees points toward a fee convention. A discrepancy isolated to cold storage points toward its receipt history. These are leads, not proof: different mistakes can produce the same difference.
The last test simply removes the reward row. In a real export, a row may disappear when one file uses UTC and another uses local time around midnight. Normalize timestamps before filtering. Preserve the original timestamp and timezone alongside the normalized value so the conversion can be checked.
Build an import mapping that survives a second export
Import fields worth preserving
Field
Purpose
Common mistake
Source row ID + account
Detect re-imports
Deduplicate by amount alone
Timestamp + timezone
Apply one cutoff
Treat local time as UTC
Asset + signed amount
Reconcile quantity
Mix USD and LTC columns
Fee + fee asset
Deduct each charge once
Subtract a fee already in the amount
Transfer ID / txid / output
Match both sides
Use a batch txid as a unique customer payment
Opening / closing balance
Independent control
Adjust until the numbers look right
Deduplicate by a stable source identifier and account, not by date and quantity alone. Two legitimate purchases can have identical amounts. A can also produce several execution IDs: an order ID is not a safe substitute for the individual fill ID. If an export changes its row identifiers, compare the full source record and quarantine uncertain matches rather than silently discarding them.
Keep quantities as exact decimal strings or integer . One LTC is 100,000,000 litoshis. Avoid binary floating-point arithmetic for a final equality check: an apparent difference of a few machine decimals should not become an invented adjustment transaction. Also keep the provider's rounding precision; do not assume a rounded screen balance is a statement to eight decimal places.
Handle unresolved differences explicitly
Create an exceptions list with account, asset, unexplained quantity, first mismatching timestamp, evidence and next action. Work forward from the last balance that reconciled. The earliest divergent row is usually more useful than examining the entire history repeatedly.
For an exchange withdrawal, compare the account debit, stated and actual credited output. The exchange's withdrawal charge need not equal the paid by the exchange's batched transaction. For a failed withdrawal, locate any reversal row. For a pending deposit, check both the required and the provider's crediting status before treating the coins as lost.
If all transaction history is unavailable, record the opening balance as an opening balance with an evidence note. That may be enough to reconcile quantities from a chosen date onward. It does not establish a historical acquisition cost. Unknown cost should remain unknown until it is reconstructed; zero is a numerical assertion, not a placeholder.
What to enter into the Litecoin.watch portfolio
The portfolio tracker now records buys, sells and internal transfers across named accounts. Enter the LTC amount received by the destination and the extra network or withdrawal fee; the source loses their sum. A balance check compares the recorded end-of-day balance with a wallet or exchange statement without automatically adjusting your holdings. remains pooled across accounts.
Use the transfer entry for moves between your own accounts. Buying and selling coins to imitate a transfer would distort the cash-flow history. The tracker still does not import arbitrary exchange CSV formats or model external gifts, rewards and borrowing. Its own JSON backup contains accounts, transactions, pre-trade valuations and balance checks; its CSV export contains transactions. The research CSV supplied in this guide remains a separate worksheet and is not a tracker import file.
Download the ten-row ledger CSV, six error results and Python calculation script. Save the script as reproduce-calculations.py in an empty folder and run python reproduce-calculations.py. It uses Python's standard library, makes no network requests and writes its teaching datasets in that folder. It does not read your wallet or exchange files.
Acceptance criteria: exchange 5.229 LTC; hot wallet 4.2498 LTC; cold storage 1.2499 LTC; combined 10.7287 LTC; every transfer has two principal legs; all ten source row IDs are unique. For your own accounts, replace those targets with independently obtained statement balances at the same cutoff.
Frequently asked questions
Should an internal transfer change my profit?
Moving coins between accounts inside the same portfolio is not a purchase or sale. Its fee can reduce value. A transfer crossing your chosen reporting boundary must be treated as an external flow for performance measurement.
Can I fix a mismatch with an adjustment row?
Use an adjustment only when its reason and evidence are recorded. An unexplained balancing entry hides the problem and can corrupt later cost and performance calculations.
Sources and method
The ledger, fault injections and decimal reconciliation are original Litecoin.watch teaching work, checked on 22 September 2026. Provider field definitions were checked against Kraken's ledger field reference and its ledger/trade comparison linked above. The exercise does not use customer data, observed trading prices or actual exchange fees.
Exchange
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 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 Keeping signing keys offline while the LTC itself remains recorded on the blockchain.
Keeping signing keys offline. Coins remain recorded on the blockchain, not inside a device. Cold storage reduces some online attack risks but still depends on secure generation, backups and correct transaction verification.
For example An offline signing device can approve a transaction while a separate connected device broadcasts it.
Common mistake Assuming that an offline device makes a lost backup, exposed recovery phrase or unchecked destination harmless.
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 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.
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 Committing funds to help validate a proof-of-stake network, with possible rewards and penalties; Litecoin has no native staking.
Committing funds under a proof-of-stake network's validator rules, potentially earning rewards and being exposed to penalties. Litecoin uses proof of work, so depositing LTC in a yield service is not native Litecoin staking.
For example An app offering yield on deposited LTC is offering a separate service; your LTC is not becoming stake that secures Litecoin.
Common mistake Treating an advertised LTC staking rate as native Litecoin income or assuming deposited coins remain under your own control.
In brief A wallet with spending keys on an internet-connected device, exposing those keys to online device risks.
A wallet whose signing keys are available on an internet-connected device. It is convenient for regular payments, but malware or a compromised device can put those keys at risk.
For example A mobile wallet that can sign and send a payment while the phone is online is a hot wallet.
Common mistake Assuming a device lock or app password replaces a recovery backup or prevents every form of malware.
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 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 Only part of the quantity requested in an order has actually traded.
Execution of only part of an order quantity. The remaining quantity may stay open, expire or be cancelled according to the order instructions. Different fills can have different prices and fee classifications. Use the filled quantity and completed trade details when recording a purchase, rather than assuming the requested order size was bought.
For example A fictional order requests 3 LTC but has filled 1.2 LTC. The other 1.8 LTC is still unexecuted; it is not part of the completed purchase record.
Common mistake Recording the full requested amount as owned while part of the order remains unfilled.
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 A service's charge for moving LTC out, which can differ from the network fee and reduce what the recipient receives.
A charge a service quotes for moving LTC out of your account. Its rules determine the fee, minimum and amount received. A service can batch several withdrawals into one transaction, so one customer's quoted charge need not match the transaction's network fee. Check the final account debit and recipient amount before confirming.
For example If a service deducts a hypothetical 0.001 LTC fee from a 1 LTC withdrawal, the recipient receives 0.999 LTC; other services may quote the debit differently.
Common mistake Assuming an exchange charge is the network's fixed fee, or confirming without checking the final recipient amount and minimum.
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 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 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 The acquisition cost assigned to coins under a chosen record-keeping method, which can differ from their current value.
Recorded acquisition cost allocated to coins still held or disposed of under a chosen method. Entered fees and historical currency conversions can affect it. A tracking tool's basis is not automatically the basis required for your tax filing; missing records or a different method can change the result.
For example If a sold quantity has $30 of allocated basis and produces $40 after selected selling fees, its recorded realized gain is $10.
Common mistake Confusing current market value with acquisition cost, or assuming every calculator uses the same fee treatment and lot-allocation method.
No separate completed review is recorded for this article. The byline identifies its author or responsible editor; it does not imply independent verification.
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.
