There seem to be some irregularities with Blockchain.info's transaction timestamp (aka Received Time
) for a set of blocks. The transaction times are recorded with unix timestamps well into the future (2017, 2022, 2035, etc..)
For example, here is a transaction in block 237173 with a timestamp of 2035-05-27 00:00:59.
All the blocks that have transactions with a future Received Time
are as follows:
237173 237175 237180 237181 237182 237183 237184 237185 237186 237187 237188 237189 237190 237191 237192 237193 237194 237195 237196 237200 237201 237202 237210 237280 237945 237980 238008 238013 238038 238227 239127 240078 241223 260657 260819
1) Are these valid transactions?
2) If they are valid, how can I assign a valid timestamp to these transactions? Would it be 'fair' to simply assign them the block's timestamp?
3) From what I understand about the Received Time
, it represents the time that bc.info sees the transaction, so how can this this timestamp be occurring? Is it a bug?