Litecoin transaction fees

Spend the same selected inputs either directly in a later payment, or consolidate them into one UTXO now and spend that UTXO later. The later payment has a recipient and a change output, both using the selected output type. For P2SH, the new input is assumed to be nested SegWit.

Consolidation links inputs under common ownership and needs enough value to pay its own fee. This comparison assumes no new inputs, dust outputs or change from the consolidation itself. It is unavailable in signed-size mode because virtual size alone does not describe the input structure. A modeled saving does not establish that the inputs are spendable or that a transaction will relay or confirm.

Transparent single-signature transactions with compressed public keys and 72-byte signatures including the sighash byte. Actual signature length can change the final size. Legacy inputs use 148 base bytes; nested SegWit 64 base bytes plus 108 witness bytes; native SegWit 41 plus 108. Output sizes are 34, 32 and 31 bytes respectively.

Weight = 4 × stripped size + witness size, including marker, flag and empty witness stacks for legacy inputs in a mixed transaction. Virtual size rounds weight up to the next multiple of four. Input and output counters use CompactSize encoding. The final fee rounds up to a whole litoshi. The model rejects weights above the usual 400,000-unit standardness limit; that is not a guarantee that every smaller transaction will relay.

Use your wallet's input script type, not the address prefix alone. Native here means P2WPKH; the ltc1q prefix also covers P2WSH, which is not modeled. Select nested only if the wallet confirms P2SH-P2WPKH. Multisig, Taproot and MWEB are not modeled. Wallet policy, dust limits and exchange withdrawal charges are separate. Check the signed transaction preview before sending.

References: BIP 141 serialization and weight; Litecoin transaction format. Learn UTXOs and coin control.