<p>That looks like a glitch with blockchain.info, there is no "time" encoded in a bitcoin transaction itself so that number is likely just when blockchain.info received the transaction. </p>

<p>In general though, it is possible to create a transaction which is only valid after a certain point in time or a certain block height in the blockchain, by using the "locktime" component of a transaction. If a locktime on the transaction is set, the transaction can only be included in a block after that point, not before, which may be of interest to you.</p>

CC BY-SA 3.0
2017-12-05T05:53:15.470Z
If you check the very last lines of the raw transaction, you can find the 'time' field with the value of 2953429233. And the 'lock_time' is set to 0. Here is another transaction like the one from my original post: https://blockchain.info/rawtx/da71fda48795fbdf05ca522ceaa7ac34bef68ca6973f33ff5ec764bdfcff045c And again, "lock_time": 0, "time": 1574921809
GSazheniuk
CC BY-SA 3.0
2017-12-05T09:31:47.307Z
@GSazheniuk yes, but then"time" field is something blockchain.info has made, it is not part of the raw transaction, that's what I said in my answer
meshcollider
CC BY-SA 3.0
2017-12-05T10:55:55.203Z
Blockchain.info is a private website, it's not the block chain, most of the information they show is fairly nonsensical. They've a history of displaying misleading, incorrect, or just plain ridiculous things about transactions.
Claris
CC BY-SA 3.0
2017-12-05T21:06:46.223Z
@MeshCollider Just our of curiosity - did you check raw transaction in any other source(s) when you said that 'there is no "time" encoded in a bitcoin transaction itself '?
GSazheniuk
CC BY-SA 3.0
2017-12-05T22:08:02.390Z
@GSazheniuk I'm very familiar with the raw transaction format :) you can see the two transaction serialisation formats here: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#transaction-id
meshcollider
CC BY-SA 3.0
2017-12-05T05:39:14.380Z
2017-12-05T05:39:14.380Z
meshcollider
<p>I just came across this Transaction: <a href="https://blockchain.info/tx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c" rel="nofollow noreferrer">https://blockchain.info/tx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c</a></p>

<pre><code>Received Time:  2063-08-04 05:00:33
</code></pre>

<p>Raw Transaction: <a href="https://blockchain.info/rawtx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c" rel="nofollow noreferrer">https://blockchain.info/rawtx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c</a></p>

<p>Is it just one case, maybe some kind of bug, which has already been solved, or is this a normal behavior?</p>

<p>Is there any official information regarding this topic?</p>

<blockchain><blockchain.info><raw-transaction>
Can you specify a date in the future for the Bitcoin transaction
GSazheniuk
# Can you specify a date in the future for the Bitcoin transaction

(Asked by: username_0 on 2017-12-05)

I just came across this Transaction: https://blockchain.info/tx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c
Received Time:  2063-08-04 05:00:33

Raw Transaction: https://blockchain.info/rawtx/cf77c2b888916c0debfb801d3d129ba5b7f6445e0dd6db9238b313b51369024c
Is it just one case, maybe some kind of bug, which has already been solved, or is this a normal behavior?
Is there any official information regarding this topic?

**Tags:** blockchain, blockchain.info, raw-transaction


---

## 1 answers

### Answer by username_1 on 2017-12-05. Score: 3 | Accepted answer

That looks like a glitch with blockchain.info, there is no "time" encoded in a bitcoin transaction itself so that number is likely just when blockchain.info received the transaction.

In general though, it is possible to create a transaction which is only valid after a certain point in time or a certain block height in the blockchain, by using the "locktime" component of a transaction. If a locktime on the transaction is set, the transaction can only be included in a block after that point, not before, which may be of interest to you.

> **Comments:**
> **username_0**: If you check the very last lines of the raw transaction, you can find the 'time' field with the value of 2953429233. And the 'lock_time' is set to 0. Here is another transaction like the one from my original post: https://blockchain.info/rawtx/da71fda48795fbdf05ca522ceaa7ac34bef68ca6973f33ff5ec764bdfcff045c And again, "lock_time": 0, "time": 1574921809  
> **username_1**: @username_0 yes, but then"time" field is something blockchain.info has made, it is not part of the raw transaction, that's what I said in my answer  
> **username_2**: Blockchain.info is a private website, it's not the block chain, most of the information they show is fairly nonsensical. They've a history of displaying misleading, incorrect, or just plain ridiculous things about transactions.  
> **username_0**: @MeshCollider Just our of curiosity - did you check raw transaction in any other source(s) when you said that 'there is no "time" encoded in a bitcoin transaction itself '?  
> **username_1**: @username_0 I'm very familiar with the raw transaction format :) you can see the two transaction serialisation formats here: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#transaction-id  

---

