MWEB
| Activation height | 2,215,584 |
|---|---|
| Chain tip | 4,926,138 |
| MWEB supply | 1792942.00025556 tLTC |
| MWEB output set | 7,593 confidential outputs to date |
MWEB amounts inside the extension block are confidential. Only peg-ins (public into MWEB) and peg-outs (MWEB back to public, carried by each block's HogEx integration transaction) have visible amounts on the canonical chain.
TestnetScan maps the public peg boundary (peg-ins, peg-outs and supply) from its own node. Its sister project MWEBscan adds the analysis layer on top: round-trip linking, privacy scoring and entity attribution.
These are inferences from public-chain data, not proof. Peg-outs are correlated to earlier peg-ins by amount and timing. Data from MWEBscan (CC BY 4.0).
How well does a peg-out amount blend in? A common, round amount hides in a larger anonymity set; an exact or unusual amount is easier to link back to its peg-in.
The anonymity set is every unspent output living inside MWEB, and a peg-in blends with all of them. On testnet the set is small and traffic is sparse, so timing and round-number amount correlation are far easier than on Litecoin mainnet. Treat testnet MWEB as a functional rehearsal, not a privacy guarantee.
| Height | Age | Peg-in | Peg-out | MWEB supply | HogEx |
|---|---|---|---|---|---|
| 4,926,138 | 4 min ago | - | - | 1792942.00025556 | 1b97528751...029fa6ae |
| 4,926,137 | 9 min ago | - | - | 1792942.00025556 | 13639a6359...b2eb31c5 |
| 4,926,136 | 14 min ago | - | - | 1792942.00025556 | 4708d2d8fd...86a7ce8b |
| 4,926,135 | 19 min ago | - | - | 1792942.00025556 | 63eb32206b...c5f23835 |
| 4,926,134 | 24 min ago | - | - | 1792942.00025556 | c77a1f16f1...47e5c3f3 |
| 4,926,133 | 29 min ago | - | - | 1792942.00025556 | 7d69bf0ce1...347217cc |
| 4,926,132 | 34 min ago | - | - | 1792942.00025556 | 8195e8c57b...b2aad746 |
| 4,926,131 | 39 min ago | - | - | 1792942.00025556 | 334555b2c2...02367f64 |
| 4,926,130 | 44 min ago | - | - | 1792942.00025556 | 1160c3d600...bfeba00b |
| 4,926,129 | 50 min ago | - | - | 1792942.00025556 | 84ce1babed...91ae69a9 |
| 4,926,128 | 55 min ago | - | - | 1792942.00025556 | 281c2bf44f...11540bbf |
| 4,926,127 | 1 hr ago | - | - | 1792942.00025556 | 660de1053a...62211e8d |
| 4,926,126 | 1 hr ago | - | - | 1792942.00025556 | 8b0fcf0515...998d8443 |
| 4,926,125 | 1 hr ago | - | - | 1792942.00025556 | 5a7a309478...aefa927d |
| 4,926,124 | 1 hr ago | - | - | 1792942.00025556 | 5020f32479...a862e762 |
| Destination | Peg-outs | Total | Blocks |
|---|---|---|---|
| tltc1qyzmtje...gyza6h | 83 | 1.19987706 | 3,400,546-3,404,092 |
| QPFTevtLvppg...bWhR6P | 76 | 0.89800000 | 3,402,668-3,421,862 |
| tltc1qwnrwys...atnwgp | 51 | 1.96013714 | 3,400,723-3,404,092 |
| tltc1qcmc9at...35aluh | 16 | 15.71428674 | 3,057,520-3,060,483 |
| tltc1qe0fudg...usjs2q | 6 | 0.40400000 | 2,389,170-2,392,147 |
| QNGyw2SNtVfW...eLYdga | 5 | 52.02000000 | 2,296,355-2,299,059 |
| tltc1qhsps9d...xnjhmg | 5 | 5.00000000 | 2,239,547-2,279,254 |
| QhN4kLyomdqZ...wdrMqb | 5 | 4.99977680 | 2,298,922-2,299,060 |
| tltc1qkge0cf...xz73eu | 3 | 5.69894349 | 4,867,633-4,877,803 |
| tltc1q28p4ep...xp7vhc | 3 | 4.00000000 | 2,298,915-2,299,060 |
| QY71rwqDiHHZ...St5TBS | 3 | 2.74181510 | 3,052,484-3,059,080 |
| tltc1qfcwu74...avu5sg | 2 | 15835.30000000 | 2,259,353-2,260,014 |
Public addresses that received more than one MWEB peg-out. Reusing an address for multiple exits links those withdrawals to a single identity and undoes much of MWEB's privacy. Use a fresh peg-out address each time (see the guide below).
What is public and what is private
- Public on the canonical chain: a peg-in's amount and the ordinary Litecoin address that funded it; a peg-out's amount and destination address; and the block's absolute MWEB supply (each HogEx
vout[0]). - Confidential inside MWEB: individual amounts (Pedersen commitments), ownership, and the transaction graph. Once value crosses the peg-in boundary, on-chain observers no longer see who pays whom or how much.
- The boundary is the weak point. Privacy comes from what happens between a peg-in and a peg-out. The two public endpoints are where amounts and timing can still be correlated.
Privacy best practices
- Let coins rest. Time between peg-in and peg-out grows the set of MWEB activity you could be confused with. Immediate round-trips link the two ends by timing.
- Avoid round numbers. Pegging in exactly 10.00 and later out exactly 10.00 (or 9.99 after fees) is a giant fingerprint. Vary amounts.
- Split and recombine. Break a large peg-in into several unrelated peg-outs at different times, and use fresh addresses for each.
- Use a fresh peg-out address that has never touched your public, doxxed, or exchange addresses; reuse re-links your shielded funds to a known identity.
- Prefer spending inside MWEB over pegging back out whenever the recipient supports it; every peg-out is a public event.
Common mistakes that deanonymize you
- Round-trip linkage: peg in X, then peg out ~X a few blocks later; amount plus timing ties the two public transactions together.
- Amount fingerprinting: an unusual, precise value (e.g. 3.14159) that appears as both a peg-in and a later peg-out is trivially matched.
- Small anonymity set: on a quiet testnet with few peg events per day, even coarse timing correlation often uniquely identifies a flow.
- Address reuse: pegging out to an address that also appears in your public chain history collapses the privacy MWEB just gave you.
These are educational heuristics for testnet experimentation, not financial or security advice. MWEB hides amounts and ownership inside the extension block; it cannot un-see the public amounts you peg across the boundary.
Read-only JSON under /ltc-testnet/api/mweb/: tip, block/:hash, blocks, pegins, pegouts, supply, clusters.
Send and receive MWEB on the Litecoin testnet with TestnetWallet.