<p>Yes, they are the same. <code>nLockTime</code> is the name used in the Bitcoin Core source code (e.g. <a href="https://github.com/bitcoin/bitcoin/blob/3c098a8aa0780009c11b66b1a5d488a928629ebf/src/primitives/transaction.h#L184" rel="nofollow noreferrer">here</a>) , whereas <code>locktime</code> or <code>lock_time</code> might be more common in JSON input/output or other pieces of software. The Bitcoin Core RPC uses <code>locktime</code> for example, and blockchain.info uses <code>lock_time</code> in its <code>rawtx/</code> endpoint</p>

CC BY-SA 3.0
2017-11-17T08:23:42.873Z
2017-11-17T08:34:36.143Z
2017-11-17T08:34:36.143Z
meshcollider
<p>I understand how 'lock_time' field work in transaction data structure, but I also see some people talking about 'nLockTime' with similar function. So are they the same? </p>

<transactions><bitcoin-core>
Is 'nLockTime' equal to 'lock_time' in transaction data structure?
Anderson
# Is 'nLockTime' equal to 'lock_time' in transaction data structure?

(Asked by: username_0 on 2017-11-17)

I understand how 'lock\_time' field work in transaction data structure, but I also see some people talking about 'nLockTime' with similar function. So are they the same?

**Tags:** transactions, bitcoin-core


---

## 1 answers

### Answer by username_1 on 2017-11-17. Score: 1 | Accepted answer

Yes, they are the same. `nLockTime` is the name used in the Bitcoin Core source code (e.g. [here](https://github.com/bitcoin/bitcoin/blob/3c098a8aa0780009c11b66b1a5d488a928629ebf/src/primitives/transaction.h#L184)) , whereas `locktime` or `lock_time` might be more common in JSON input/output or other pieces of software. The Bitcoin Core RPC uses `locktime` for example, and blockchain.info uses `lock_time` in its `rawtx/` endpoint


---

