Dotted-underlined terms open a quick definition. Close it to keep reading.
We sorted the decoded transparent outputs of 14,278 transactions in 50 consecutive . Every entry in the naive top ten, after removing , contained the special MWEB HogAddr output. A headline calling these the ten biggest transfers would have classified protocol accounting as ordinary transfers.
The largest ordinary output total in this window was 22,351.31551018 LTC. That still does not tell us that somebody paid another person that amount. Its two outputs were 1.42123174 LTC and 22,349.89427844 LTC; neither output is labelled “payment” or “change” by the chain.
Correction, 2 October 2026: the earlier edition offered an all-time list with unsupported owner labels and historical dollar values. This replacement publishes a bounded, reproducible ranking and the exact classification that changes its result.
The sample and the two rankings
Frozen mainnet window; no all-history claim
Measure
Result
Block range
3,188,200–3,188,249 inclusive
Decoded transaction rows
14,278
Coinbase rows removed
50
Rows with a witness_mweb_hogaddr output
50
Remaining ordinary transaction rows
14,178
HogAddr rows in the naive top ten
10 of 10
Largest naive non-coinbase output total
426,662.68372612 LTC
Largest ordinary output total
22,351.31551018 LTC
Same blocks, different classifications. Both bars start at zero. Neither is a measure of money paid to an identified recipient. Download SVG.
Why HogEx changes the result
HogEx links the extension block to the transparent chain. In the pinned Core implementation, its first output is HogAddr and the remaining outputs are peg-outs. Inspect the validation rules. The large carried output is therefore not an ordinary single-person payment every time a new block appears.
Our classifier checks whether any decoded output has scriptPubKey.type == "witness_mweb_hogaddr". That label is defined in Core’s script-type names. We publish the label on every captured row instead of silently deleting it. The ordinary ranking excludes both these rows and coinbase rows, then sorts the sum of serialized transparent output values.
At height 3,188,209 the largest naive row contained 426,657.68372612 LTC in its HogAddr output and five additional 1 LTC outputs. Its sum was 426,662.68372612 LTC. Counting the whole sum as the reserve would also be wrong: the extra outputs must remain separate.
The ten largest ordinary output totals in these 50 blocks
Ranked by summed transparent outputs, not by net transfer between owners
Several rows have nearly the same large output followed by a . The captured data establishes the amounts and identifiers. It does not establish an label, a common legal owner, a sale, or a market impact. The CSV contains full so another researcher can inspect rather than trust our abbreviations.
Three ways an output-total headline can mislead
Change: spending a large input can create a small recipient output and a large return output. Total outputs can be much larger than the intended payment.
Self-transfers and batches: rearranging and paying several people can share the same outward appearance. counts are not user counts.
Protocol transactions: HogEx reserve accounting needs its own category. Including it in ordinary rankings changes which rows appear at the top.
A usable “largest transfer” study would need an explicit definition of economic transfer, a defensible change-identification method and uncertainty around owner labels. This report intentionally stops at observable output totals.
What to check before acting on a whale alert
Start with the transaction ID in the transaction checker. Check the output scripts, whether the row is coinbase or HogEx, the actual output split and the confirming block. Then inspect the source and timestamp of any exchange attribution. A large amount alone is not evidence of buying pressure or selling pressure.
The versioned package keeps its capture boundary. It will not silently become a live quote. Download the files into one folder and run python analyze.py.txt .. The script validates input hashes before calculating the published results. A successful rerun checks the arithmetic on this export; it does not independently validate our or prove that the sample represents the whole network.
Reviewed against the linked materials on 2 October 2026. Calculations and drafting were AI-assisted; no independent external review or personal attendance is claimed. Original publication date retained. See our corrections policy.
Litecoin (LTC)
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 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 block's special first transaction, used to claim newly created LTC and fees rather than spend ordinary earlier outputs.
The special first transaction in a block through which its creator can claim the allowed block subsidy and transaction fees. It does not spend ordinary previous outputs. Its spendable outputs are subject to coinbase maturity. This protocol term is separate from the similarly named exchange.
For example A block explorer shows a mining reward in the block's coinbase transaction. A later pool payout can be an ordinary transaction spending matured coins.
Common mistake Assuming an exchange withdrawal is a coinbase transaction because of the service's name, or treating newly mined outputs as immediately spendable.
In brief An informal name for a large holder; a large transfer alone does not identify a holder or prove a trade.
An informal term for a holder with a large cryptocurrency position; there is no universal LTC threshold. A large-transfer alert reports an observed transaction or output total, not the identity or net holdings of a person. Such activity can be exchange housekeeping or wallet reorganization rather than a market purchase or sale.
For example A large transfer between two exchange-controlled addresses may be a custody reorganization rather than somebody buying LTC.
Common mistake Predicting a purchase, sale or price move from the transferred amount alone.
In brief Litecoin's optional layer that conceals amounts inside it, while base-chain and boundary activity can still reveal information.
Mimblewimble Extension Blocks, activated on Litecoin in May 2022. MWEB conceals amounts inside the extension layer; the base chain and boundary transfers can reveal information. Use maintained software and review the 2026 security postmortem.
For example An MWEB transfer uses compatible software and a different address format from an ordinary transparent Litecoin transfer.
Common mistake Assuming every LTC wallet or exchange accepts MWEB addresses, or that optional privacy removes all possible information leaks.
In brief An output a node's relay rules regard as too small to spend economically, with no single universal amount.
A transaction output so small that a node's relay policy treats it as uneconomical to spend. The threshold depends on the output type and policy settings. It is not a universal minimum payment, and services may set different minimums.
For example A tiny leftover output may be rejected as dust even though your main payment is large enough.
Common mistake Copying one quoted dust number as a minimum for every address type, wallet, exchange or node setting.
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 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 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 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 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.
Downloadable data or code · Observed data / replay.
Content review recorded: 2026-10-02. 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.
Next scheduled review: 2026-11-01. This review is due.
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.
