<p>Timestamps in Bitcoin, including block timestamps and nLocktime values, are unsigned 32-bit.</p>
<p>The last possible timestamp is Feb 7th 2106, at 06:28:15 UTC.</p>

CC BY-SA 4.0
2021-11-11T18:44:28.753Z
That is good to hear that nLocktime will not be affected then. Thankyou
krogoth
CC BY-SA 4.0
2021-11-11T18:17:30.730Z
2021-11-11T18:17:30.730Z
Pieter Wuille
<p>So UNIX END TIME is January 19, 2038.</p>
<ul>
<li><p>What will happen then to the btc TX that looks at Unixtime for nLOCKTIME transactions?</p>
</li>
<li><p>Will any Locktime transaction past that date, say to 2040 be an issue? Or will blockchain continue adding to the Unix time like there was no end date?</p>
</li>
</ul>

<bitcoin-core><blockchain><timestamp><locktime><hash-time-locked-contract>
UNIX END TIME January 19, 2038 - Will it affect Timelock nLOCKTIME smart contracts past that date?
krogoth
# UNIX END TIME January 19, 2038 - Will it affect Timelock nLOCKTIME smart contracts past that date?

(Asked by: username_0 on 2021-11-11)

So UNIX END TIME is January 19, 2038.

* What will happen then to the btc TX that looks at Unixtime for nLOCKTIME transactions?
* Will any Locktime transaction past that date, say to 2040 be an issue? Or will blockchain continue adding to the Unix time like there was no end date?

**Tags:** bitcoin-core, blockchain, timestamp, locktime, hash-time-locked-contract


---

## 1 answers

### Answer by username_1 on 2021-11-11. Score: 4 | Accepted answer

Timestamps in Bitcoin, including block timestamps and nLocktime values, are unsigned 32-bit.

The last possible timestamp is Feb 7th 2106, at 06:28:15 UTC.

> **Comments:**
> **username_0**: That is good to hear that nLocktime will not be affected then. Thankyou  

---

