Guide

Why a Litecoin block can have an earlier timestamp than its parent

Block 858’s timestamp went back 13 seconds. Rebuild the 11-header median to see why it passed and which clock to use for payment confirmations.

Why a Litecoin block can have an earlier timestamp than its parent

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

Open 858 and its parent side by side. The parent says 03:40:49 UTC on October 13, 2011. Its child says 03:40:36, 13 seconds earlier. Follow the child’s previousblockhash and it leads straight back to block 857. The timestamps run backwards while the chain links point in the expected order. Block 858 in Litecoin Space.

Where the 13 seconds went

Litecoin Core compares an incoming header’s time with the median time past (MTP) of its parent. At height 858, that means sorting the raw timestamps from heights 847 through 857 and taking the sixth value. We pulled the 12 consecutive headers from our early-chain archive, checked their parent links and recomputed the median. Download the archived headers. Read the Litecoin Core check.

ValueUnix secondsUTC
Parent header time, block 857131847724903:40:49
Parent MTP, sixth value from blocks 847–857131847723503:40:35
Child header time, block 858131847723603:40:36

The child passed the lower-bound check by exactly one second, the smallest possible margin. A child timestamp of 03:40:35 would have failed because the rule requires a value strictly above the parent’s median. Core also checks the upper bound and rejects a timestamp more than two hours ahead of the ’s adjusted time. How Core computes the median. The two-hour limit.

Reproduce it on a Litecoin node

On a synced mainnet node, run these read-only commands in a shell. The first two show the parent link and both time fields. The last command uses jq to extract the 11 timestamps and sort -n to put them in numeric order.

litecoin-cli getblockheader "$(litecoin-cli getblockhash 857)"
litecoin-cli getblockheader "$(litecoin-cli getblockhash 858)"
for h in $(seq 847 857); do
  litecoin-cli getblockheader "$(litecoin-cli getblockhash "$h")" | jq -r '.time'
done | sort -n | sed -n '6p'

The last line prints 1318477235, which matches mediantime in the response for block 857. The response for block 858 has its own mediantime, 1318477236, because its window starts at height 848 and includes block 858. Use the value from block 857 when checking block 858’s lower bound. Litecoin Core RPC implementation.

A second example from 2026

On June 12, 2026, the timestamp of block 3,123,826 read 12:58:44 UTC, two seconds earlier than its parent at 12:58:46. We traced the parent hashes and recomputed that parent’s median from blocks 3,123,815 through 3,123,825. It was 12:49:15, leaving the child 569 seconds above the lower bound. Read the block in Litecoin Space. Cross-check the header in BlockCypher.

Choose the clock that answers your question

  • Which block confirms the payment? Follow the block hash and height on the active chain. The block containing the transaction counts as the first .
  • How long did the payment wait? Record when your node first sees the transaction and when it first sees it included in a block. A polling collector measures when it observed those events, so include its polling interval when reporting precision. See how Litecoin.watch measures confirmations.
  • What do the header timestamps show? Subtract one header time from the next to measure the difference between the recorded timestamps. Keep signed differences in raw data and document any exclusions when summarizing them. In the example above, −13 seconds describes the two timestamps. The headers alone cannot tell you how long the nodes waited or how fast the blocks propagated.

Sources checked November 16, 2026. Cover illustration generated with AI.

Method and data

Downloadable data or code.

Content review recorded: 2026-11-16. 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: 2027-02-14.

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