I’ve been running a private Bitcoin mainnet (using Bitcoin Core 24.0.1) and noticed an issue with transaction locktime values that don’t match the expected previous block height.
I’ve conducted several tests, and here are some results:
Transaction edf5074c254c931dab22839c53d8fb14c51df3ea396af44708730bde787d94ac has locktime = 0
Transaction dd08dae7a92a6ce9e15831d795f5979ed73eef11663b25373b0296b52a4ce89c has locktime = 225
Transaction f6df6ed25dc2981b382edcefaa96acd8683d3335bfc0ae97514517f963283a2b has locktime = 225
Transaction f3aabca224b1b219c6c39d99a67acb17e89bb5bf895dddb5adc1a47e90849727 has locktime = 225
Transaction 33fb1557436488563827b7b5ed2d623990593909599bdf350f32b8511aa95cc6 has locktime = 225
Transaction 4d38665db6e9d655c5d2d7ac1ed29aa729be0b0cedd14f3860bfe39c3a39728a has locktime = 225
Transaction 7b876b6fdce46c85c41be173db5807390aa306b0300e4135468f56c9ca32b320 has locktime = 225
Transaction d1b1612035ca73267ed4ed867b50c7db5d38eebab34240681a365c829599003f has locktime = 225
Transaction 7767b8c7b5d4f84ecfd505d2ccc1506e8ca711fc20f024606e8db640d594fd86 has locktime = 225
Transaction da1bd4dfbe776b1912a2f84b70bf410439be9f33628acdaeef6d82205a7dea69 has locktime = 225
Transaction 4cd53c3fce854297d9fe1c098172cf4e545a078cdafd6b0b36cf342a7ee200ff has locktime = 225
Transaction 9d6cc2a1020719da36a0b24d45d65f610ac42c148f65ea204f400bf10b183b04 has locktime = 225
Transaction eff4a3688d262bf36885df3e7e3cdf0ebd4b903b7524ef96892be27ac6be7061 has locktime = 225
Transaction 98bef0810cf4bf59f07cb9e1e30ad84ffafba765f3a1a1e6ba353dacc1c0820a has locktime = 225
Transaction 3063cf82d7040030894750ed7d910ea87601ff64a56f406e9b7883f1e80ae10c has locktime = 225
Transaction 28e13288f8a3312a73e26a22f509cc44de27a5ec79f89f2dac967ce26d5e0fac has locktime = 225
Transaction b7abcdea6116c79ec8249c65ee0d45fd1565ee3a4ea0bcdbb902b58b1b3081a4 has locktime = 225
Transaction 9044b01d2cdd4a535f1a2e92e0edfa0137c4c1045cf49afe74a5ef490ca72884 has locktime = 225
Transaction 044caa0d57b8d514068490958423abd292a92cd63af5818424cb1453fbb16048 has locktime = 130
Transaction 9e73910dbc8148c423c9d0885ace1093a28069c29f4f2413402f85fd661a990f has locktime = 225
Transaction b7d68e4207e60b9d57819bb65943f32dcf6c7ea1b350f3508c68202c18381211 has locktime = 225
Transaction e23a76a284a560093d527a5b85a59d7ab9f3e058e85a45983f43dbdb4250ea17 has locktime = 225
Transaction ae9345f519a418c8ede72639eef3af33c0f34ff84a7ee50cd9cb30f62a7f2b95 has locktime = 225
Transaction 9884756dc6b30b206d75bdbef17961f995b0e38760afb2c9d537a7ac9ba26fca has locktime = 225
Transaction 81fc01a483702c6dfb5a4c6883a74bf02d8b651c270786a83a4555fcba417f25 has locktime = 225
Transaction c8e2b83d3396f37aae4152de1b82c50073c43811080a1eabf2bf4cf7913a5123 has locktime = 225
Transaction f70e375a65b903f1ecd25b32c156f89f74ac5bd96e78669715ad2db7b422054c has locktime = 225
Transaction e60c36f2bd993149ade61cbf6496c778544290ddabb4834e08eae5c6cf0e6a28 has locktime = 225
Transaction a2d43414476684ff0c455a9e3194419f0c1774ad0da1b719467ed2fb7eaf8823 has locktime = 225
Transaction f75983a60cb37f59dd5521039740c530499e444fa3dfdd82984ac4c3a2cd8063 has locktime = 225
Transaction 95017671959ae445411ecf283d1022edb89824352485b912e4274cca6bdb1047 has locktime = 225
Transaction a285915263bcf26120cf1025741ab6b062c4b3daff482a52a309df52e132d9c0 has locktime = 225
Transaction 06424b8319c59070fa24a6a8dceb046fac4678866b974f72bdf44f83bce6259d has locktime = 225
Transaction 1ef4d104efba0d3be5a3f065263318e3a630dbf8bbed1ca746a05072d86b86b3 has locktime = 225
Transaction 4d1af86bbe7b5c8f935a3c79f87e7d9145d99a9b77e43a32bffb78f614385060 has locktime = 225
Transaction 5797654e226831beefc49f622beebb34fa74c4d4986ff033f98f419c3e743117 has locktime = 167
Most transactions have locktime = 225, which corresponds to the last block. However, some transactions have seemingly random locktime values (e.g., 130, 167).
What could cause these inconsistent locktime values?
