<p>There is no timestamp field in bitcoin transactions. BC.I timestamps the transaction when it comes to this service for a very first time. You should not use this value, because it can be quite incorrect/irrelevant.</p>

<p>I think that the last transactions in these blocks have not seen by BC.I in "wild" form. BC.I discovered them when they come within a block. So, it is a small bug on BC.I - it does not shows you timestamp for some txs.</p>

<p>Just live with it.</p>

CC BY-SA 3.0
2015-06-04T00:09:48.870Z
What do you mean by 'wild' form?
mrp
CC BY-SA 3.0
2015-06-04T05:20:40.563Z
Wild = Not in a block
amaclin
CC BY-SA 3.0
2015-06-01T16:41:31.497Z
2015-06-01T16:41:31.497Z
amaclin
<p>The last transaction in blocks 219882, 219888, and 219892 don't have a timestamp.  And by <em>last transaction</em> I mean the last transaction shown in the json file. </p>

<ul>
<li><a href="https://blockchain.info/block-height/219882?format=json" rel="nofollow">219882</a></li>
<li><a href="https://blockchain.info/block-height/219888?format=json" rel="nofollow">219888</a></li>
<li><a href="https://blockchain.info/block-height/219892?format=json" rel="nofollow">219892</a></li>
</ul>

<p>I find this to be a bit odd.  Does anyone know why this has occurred? </p>

<blockchain.info><timestamp>
bc.info transactions with no timestamp
mrp
# bc.info transactions with no timestamp

(Asked by: username_0 on 2015-06-01)

The last transaction in blocks 219882, 219888, and 219892 don't have a timestamp. And by *last transaction* I mean the last transaction shown in the json file.

* [219882](https://blockchain.info/block-height/219882?format=json)
* [219888](https://blockchain.info/block-height/219888?format=json)
* [219892](https://blockchain.info/block-height/219892?format=json)

I find this to be a bit odd. Does anyone know why this has occurred?

**Tags:** blockchain.info, timestamp


---

## 1 answers

### Answer by username_1 on 2015-06-01. Score: 3

There is no timestamp field in bitcoin transactions. BC.I timestamps the transaction when it comes to this service for a very first time. You should not use this value, because it can be quite incorrect/irrelevant.

I think that the last transactions in these blocks have not seen by BC.I in "wild" form. BC.I discovered them when they come within a block. So, it is a small bug on BC.I - it does not shows you timestamp for some txs.

Just live with it.

> **Comments:**
> **username_0**: What do you mean by 'wild' form?  
> **username_1**: Wild = Not in a block  

---

