Litecoin Data: Index Transactions, Addresses, and MWEB Activity
Index Litecoin transactions, outputs, addresses, and MWEB extension block activity in one pipeline, delivered to your own database. Real-time and complete history, no node to run.
Litecoin is a peer-to-peer, proof-of-work cryptocurrency on the Bitcoin model, with Scrypt mining and a block every 2.5 minutes on average. Since 2022 it has also carried MimbleWimble Extension Blocks (MWEB), an opt-in confidential transaction layer that runs alongside every main-chain block. You can read how the project frames it at litecoin.org.
That makes a Litecoin block two datasets in one: a transparent UTXO chain that reads like Bitcoin, and an extension block where amounts and addresses are hidden behind commitments. Indexing Co delivers both in each block, the transparent transactions plus the MWEB inputs, outputs, and kernels, so you can index ordinary transfers and track MWEB usage in one pipeline, delivered to your own PostgreSQL, warehouse, or webhook.
Why Litecoin data is hard
What Indexing Co delivers for Litecoin
Run a node that understands MWEB and parse both ledgers.
- Operate an MWEB-aware Litecoin Core node, or find an RPC that exposes it.
- Parse the transparent transactions and the extension block separately.
- Special-case the HogEx transaction so it does not pollute transfer data.
- Build backfill, reorg handling, and real-time delivery from scratch.
One pipeline delivers both sides of every Litecoin block.
- Transparent inputs and outputs with decoded addresses and script types.
- The MWEB extension block in the same payload: inputs, outputs, kernels, and kernel fees.
- Shaped by your transform, landed in your PostgreSQL, BigQuery, warehouse, or webhook.
- Real-time delivery plus complete backfilled history. No node to operate.
What you can index
| Litecoin data type | What it gives you |
|---|---|
| Transparent outputs | Receiving address, value, output index, and script type |
| Transparent inputs | The outpoints each transaction spends, for joining to earlier outputs |
| MWEB pool size | The HogEx output value: total LTC held inside MWEB at each block |
| MWEB block activity | Counts of MWEB inputs, outputs, and kernels, plus kernel fees |
| Block headers | Height, time, difficulty, and transaction count |
A transform, not a subgraph
You write the transform in JavaScript, not AssemblyScript, and change it without re-indexing from block zero. Indexing Co runs your function over each block server-side. This one emits transparent output rows, the MWEB pool size from the HogEx output, and a per-block summary of MWEB activity.
// Indexing Co transform: Litecoin outputs plus the MWEB extension block
function transform(block) {
const rows = [];
for (const tx of block.tx || []) {
for (const out of tx.vout || []) {
const spk = out.scriptPubKey || {};
if (spk.type === 'witness_mweb_hogaddr') {
// HogEx output: the value held inside MWEB as of this block
rows.push({
chain: block._network,
block: block.height,
kind: 'mweb_pool',
txid: tx.txid,
value_ltc: out.value,
});
continue;
}
const address = (spk.addresses || [])[0];
if (!address) continue;
rows.push({
chain: block._network,
block: block.height,
kind: 'output',
txid: tx.txid,
output_index: out.n,
to_address: address,
script_type: spk.type,
value_ltc: out.value,
spends: (tx.vin || []).filter((input) => input.txid).length,
});
}
}
// MWEB amounts are hidden behind commitments; counts and kernel fees are public
const mweb = block.mweb || {};
rows.push({
chain: block._network,
block: block.height,
kind: 'mweb_block',
mweb_inputs: (mweb.inputs || []).length,
mweb_outputs: (mweb.outputs || []).length,
mweb_kernels: (mweb.kernels || []).length,
mweb_kernel_fees: (mweb.kernels || []).reduce((sum, k) => sum + (k.fee || 0), 0),
});
return rows;
}
Litecoin with Indexing Co
You want full control of node infrastructure and have the team to run an MWEB-aware Litecoin node, parse both ledgers, and build backfill and reorg handling in-house.
You want Litecoin transfers and MWEB activity delivered to your own database, on the same schema as your other chains, with real-time plus complete history and no infrastructure to run.
Related Reading
FAQ
Can Indexing Co see amounts inside MWEB?
No, and neither can anyone else without the keys. MWEB outputs are commitments, so amounts and recipients are hidden. What the block does expose is the number of MWEB inputs, outputs, and kernels, the fee on each kernel, and the HogEx output that holds the total value inside MWEB.
How do I track how much LTC is in MWEB?
Read the HogEx transaction in each block. Its output with script type witness_mweb_hogaddr holds every coin pegged into the extension block, so its value is the MWEB pool size at that height. The transform above emits it as a mweb_pool row.
Do Litecoin inputs include the sender address?
Not directly. Each input carries the transaction id and output index it spends. Because Indexing Co delivers every output, you can join inputs to the outputs they spend in your own database to recover sender addresses and values.
Do I need to run a Litecoin node?
No. Indexing Co sources Litecoin blocks, including the MWEB extension block and full history, so you never operate a node.
Where does the Litecoin data go?
Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.
Get Started
Index Litecoin in minutes. Set up your first transfer or MWEB pipeline without running a node.