Read the block countdown on an LND force closure
After a force close, funds can remain in limbo while outputs mature. The countdown is expressed in blocks, so wall-clock deadlines alone give an unreliable recovery estimate.
Locate the affected funding point
Inspect pending force-closing channels and match the original channel point. Keep maturity height and limbo balance on the same row to avoid mixing independent closures.
lncli pendingchannels | jq '.pending_force_closing_channels[] | {point: .channel.channel_point, limbo_balance, maturity_height, blocks_til_maturity, pending_htlcs}'
Handle mature but unswept funds
A positive blocks_til_maturity means more blocks are needed for the commitment output. Negative values count blocks since maturity. Even a mature output can await a sweep and confirmation. Pending HTLCs can have their own maturity stages, so inspect their individual entries before assuming that the entire balance releases together.