Guide

Litecoin mempool explained: transaction states and diagnostics

Follow a payment from local signing to mempool admission and confirmation. Read Core fields, calculate transparent fees and diagnose absence before creating another payment.

Litecoin mempool explained: transaction states and diagnostics
On this page

Dotted-underlined terms open a quick definition. Close it to keep reading.

A is one 's collection of accepted, unconfirmed transactions. There is no single global queue that guarantees a position or a completion time. A transaction can exist in a , reach one node, propagate further, enter a , disappear from a local mempool or conflict with another spend. Those states need different responses.

This guide explains how to inspect them using Core v0.21.5.8. Its RPC commands are diagnostic. Examples labelled synthetic illustrate selected fields and arithmetic; they are not live measurements or transactions you should broadcast.

Follow the transaction's state before taking action

Transaction states and the evidence each requires
StateWhat you knowUseful next check
Constructed or signed locallyThe wallet has transaction data or an authorizationDid the wallet actually submit it?
Accepted by your nodeThat node accepted the transaction under its local conditionsDependencies, fees, broadcast state and other observations
Observed elsewhereAnother observer reports the transactionIts network, observation time and confirmation status
Included in the active chainA block currently contains the transactionConfirmation depth and the recipient's crediting rules
Absent or dropped locallyYour node does not currently list itConfirmation, conflict, expiry, propagation and synchronization
ConflictedAnother transaction spends an input it usesWhich spend, if any, is in the active chain
A transaction can be created, accepted into a local mempool, included in a block, dropped or conflicted. Nodes can observe different states.
Conceptual transaction states. A local observation is not a global queue position or a confirmation deadline.

The signed-but-unbroadcast walkthrough shows why a alone is not evidence that the network received a payment. A wallet notification may describe a local operation rather than an outcome.

Why nodes can disagree

Nodes receive transactions at different times and can have different peers, resource limits and relay settings. A node may reject or evict a transaction under policy even when a block containing it could satisfy . Consensus validity, mempool admission and miner selection are separate questions.

A full mempool can apply a higher admission threshold than a quieter one. A node can also be restarting, loading retained mempool data or following a stale chain tip. A screenshot of zero pending transactions does not establish that every node has an empty queue.

The reviewed mempool implementation and RPC definitions provide the version-specific behavior. Do not assume that a newer Bitcoin RPC guide describes exactly the same Litecoin fields or policies.

Start with the node, then the transaction

Query the local Core instance that is actually connected to the intended network. If it uses a custom data directory, include the same argument used at startup. The following assumes the matching litecoin-cli is available in your shell:

litecoin-cli getblockchaininfo
litecoin-cli getnetworkinfo
litecoin-cli getmempoolinfo

Check chain, synchronization, tip freshness and connectivity before interpreting a missing transaction. If you need a setup example, use the full-node guide. A node that is behind or disconnected cannot provide a complete current diagnosis.

Selected getmempoolinfo fields in the reviewed release
FieldMeaningCommon mistake
loadedWhether retained mempool loading has completedTreating startup state as a finished observation
sizeCurrent local transaction countReporting it as the number pending everywhere
bytesSum of virtual transaction sizes under the reported accountingConfusing it with physical memory use
usage and maxmempoolCurrent memory use and its configured limitAssuming they equal the transaction-size sum
mempoolminfeeCurrent local admission rate in LTC per kBReading it as litoshis per vbyte or a confirmation guarantee
minrelaytxfeeThe reported minimum relay rateAssuming every other node and miner uses the same conditions

Use litecoin-cli help getmempoolinfo to verify your installed version's fields. The extra information exposed for MWEB-related work also needs its own interpretation; the simple fee example below is explicitly transparent.

Inspect a specific entry

Replace the placeholder with the real transaction ID you obtained from the sender:

litecoin-cli getmempoolentry "TXID_FROM_YOUR_WALLET"
litecoin-cli help getmempoolentry

If the entry exists, inspect its size, fees, unconfirmed dependencies and broadcast information. Here is a synthetic selection of fields for one transparent transaction, not a complete RPC response:

{
  "vsize": 200,
  "ancestorcount": 1,
  "descendantcount": 1,
  "fees": {
    "base": 0.00000400,
    "modified": 0.00000400,
    "ancestor": 0.00000400,
    "descendant": 0.00000400
  },
  "depends": [],
  "spentby": [],
  "bip125-replaceable": false,
  "unbroadcast": false
}

The base fee is 0.00000400 LTC, or 400 . Dividing by 200 vB gives 2 litoshis/vB. The ancestor and descendant counts include the transaction itself; a count of one in this example does not mean there is another unconfirmed relative.

depends names unconfirmed input dependencies; spentby names local unconfirmed transactions spending this transaction's outputs. The ancestor and descendant fee fields describe modified totals for their respective sets. Local fee adjustments mean those totals should not automatically be treated as actual on-chain fees paid by every participant.

The replacement field reports the version's assessment under its mechanism. A false value is not a universal promise that no competing spend can ever appear. Likewise, unbroadcast: false does not certify global propagation, miner inclusion or credit to the recipient's service account.

Convert RPC rate units explicitly

One LTC is 100,000,000 litoshis. For the transparent rate conversion used here, one kB corresponds to 1,000 , so:

Litoshis/vB = rate in LTC/kB × 100,000.

Hypothetical transparent fee-rate conversions
RPC rateConverted rateFee for a hypothetical 200-vB transaction
0.00001000 LTC/kB1 litoshi/vB200 litoshis = 0.00000200 LTC
0.00002000 LTC/kB2 litoshis/vB400 litoshis = 0.00000400 LTC
0.00005000 LTC/kB5 litoshis/vB1,000 litoshis = 0.00001000 LTC

These are conversions, not recommended rates, observed defaults or promises of acceptance. The fee guide explains why transaction construction, estimator output and service require separate treatment.

A parent and child can change the fee picture

Consider a hypothetical transparent parent of 200 vB paying 200 litoshis and a child of 100 vB paying 800 litoshis. Taken together they pay 1,000 litoshis for 300 vB, approximately 3.33 litoshis/vB. The parent alone pays 1 litoshi/vB.

This arithmetic explains why miners considering dependencies cannot always rank work by each transaction's standalone rate. It does not establish that every node will accept the package, that all miners use identical selection or that this rate is sufficient now.

requires a spendable relevant output, a wallet capable of constructing the child and acceptable policy and package conditions. instead needs a supported replacement workflow and applicable relay rules. Both can add costs and both need the actual transaction state established first.

What a missing mempool entry means

A local lookup failure has several possible explanations
PossibilityEvidence to seekAvoid assuming
It was never broadcastWallet submission record, connectivity and signed-file stateThat a displayed TXID proves network receipt
It confirmedActive-chain inclusion and the relevant outputThat leaving the mempool means payment failure
This node never accepted or retained itOther observations, admission errors and local policyThat no other copy can propagate
It was replaced or conflictedCompeting input spends and their chain statusThat the original payment and its replacement are independent receipts
The lookup used the wrong contextNetwork, identifier, wallet and data directoryThat a correct-looking string identifies the intended transfer

For your own loaded wallet, gettransaction can provide wallet-related information. Arbitrary historical lookup through getrawtransaction has different prerequisites, such as a suitable index or a known block context. A wallet-disabled, is not a universal -history service. Read the raw-transaction RPC help for the exact lookup being attempted.

Deleting a wallet entry or abandoning a local transaction does not revoke already distributed signed data. The cancellation experiment distinguishes those actions from a confirmed competing spend.

Diagnose before creating a second payment

A can still await a service's deposit credit, minimum amount, required confirmation depth or reconciliation process. Raising a fee on a different payment does not resolve that accounting state.

Record the original TXID, intended recipient, amount, observed output and current status. Contact the actual service through its verified channel when on-chain evidence and account credit disagree. Share the minimum relevant information rather than an entire wallet history or recovery material.

The duplicate-payment study separates rebroadcasting the same signed transaction from constructing a new transfer. Rebroadcasting identical transaction data and paying the merchant again are not the same operation.

MWEB visibility and observer limits

Internal confidential amounts cannot be reconstructed from an ordinary transparent explorer just because it reports a transaction count. Litecoin's mempool RPC has -related accounting, so a consumer must check its exact version and the relevant weight and fee fields before applying a transparent-only formula.

For aggregate observations, preserve the node, timestamp, polling interval, selection rules and gaps. The site's one-week observation and confirmation-time study publish their scope. Neither is a global queue monitor or an invoice settlement guarantee.

Downloads and method

Download the annotated synthetic RPC example and fee-conversion and dependency calculations (CSV). The parent-and-child worksheet records the separate package example. These files preserve the version reference, invented example inputs and exact arithmetic. No sample transaction was broadcast and no live mempool result is represented by these examples.

The diagnostic explanations were checked against the linked v0.21.5.8 code on 21 October 2026. Existing controlled studies are cited for the experiments they actually performed. Use your installed help and current node response for an operational decision.

Frequently asked questions

Is there one Litecoin mempool shared by everybody?

No. Each node maintains local state under its received data and policy. Observers can disagree temporarily or retain different sets of transactions.

Does a missing getmempoolentry result prove a payment was cancelled?

No. It may have confirmed, never reached that node, been dropped or conflicted, or been queried in the wrong context. Another copy may still propagate.

Does unbroadcast=false guarantee a miner received it?

No. It is a local broadcast-state field, not a certificate of global propagation, inclusion or recipient account credit.

Can I always use RBF or CPFP to speed up a payment?

No. Wallet capabilities, spendable outputs, transaction conditions and node or miner policies matter. Establish the original state and actual costs first.

How many litoshis per vbyte is 0.00002000 LTC/kB?

For the transparent conversion here, it is 2 litoshis/vB: multiply the LTC/kB rate by 100,000. It is an arithmetic example, not a fee recommendation.

Should I pay again when an explorer shows nothing?

First determine whether the original transaction was broadcast, confirmed, conflicted or simply not visible to that observer. A new payment can create an unintended duplicate.

Method and data

Downloadable data or code.

Content review recorded: 2026-10-21. 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.

Sources saved with the review:

See the article body for source links and any downloadable materials. Editorial method · Corrections · Report an issue

Jarosław Wasiński
Editor-in-chief · Financial markets and Litecoin education

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.

Background, selected work and editorial responsibility →

Founder of MyBank.pl Financial education and market analysis Named editorial responsibility