This bitcoin transaction was received in 1972... what?

[chriswilmer]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

[DeathAndTaxes]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

There is no timestamp in transactions.

Blockchain.info is reporting the time it(as in the blockchain server) saw the tx.  Obviously something was wrong with their clock.

[btceic]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

Warning! this transaction is a double spend of 74058000. You should be extremely careful when trusting any transactions to/from this sender.

[chriswilmer]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

There is no timestamp in transactions.

Blockchain.info is reporting the time it(as in the blockchain server) saw the tx.  Obviously something was wrong with their clock.

After 2016 blocks have been found, how is the difficulty adjusted to make finding blocks slower/faster... I thought timestamps were used for this.

[soniq]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

Warning! this transaction is a double spend of 74058000. You should be extremely careful when trusting any transactions to/from this sender.

Is there a way to block  this address from  sending or receiving coins to my wallet?

[niko]

How does this happen?

http://blockchain.info/tx/ebfbf928e861abd8c29e8123174f1f65e8a0ccf792b4a2c4bc5cba43b2a74160

I kind of understand that bitcoin miner's stamp the transactions with their own time... but accuracy doesn't matter at all, why do we even bother? Can someone explain this to me?

-Chris

There is no timestamp in transactions.

Blockchain.info is reporting the time it(as in the blockchain server) saw the tx.  Obviously something was wrong with their clock.

Block number is the timestamp. You should refer to the block the transaction was included in.

Included In Blocks    237189 (2013-05-21 11:30:02

[DeathAndTaxes]

After 2016 blocks have been found, how is the difficulty adjusted to make finding blocks slower/faster... I thought timestamps were used for this.

There are timestamps in blocks, that is used to compute the difficulty change (and blocks must be within 2 hours of network mean time or will be rejected by other nodes).

However that has nothing to do with this transaction. There are no timestamps on transactions.  Blockchain.info is simply (incorrectly) reporting the time THEY saw the transaction which even if correct will vary from node to node.

[chriswilmer]

After 2016 blocks have been found, how is the difficulty adjusted to make finding blocks slower/faster... I thought timestamps were used for this.

There are timestamps in blocks, that is used to compute the difficulty change (and blocks must be within 2 hours of network mean time or will be rejected by other nodes).

However that has nothing to do with this transaction. There are no timestamps on transactions.  Blockchain.info is simply (incorrectly) reporting the time THEY saw the transaction which even if correct will vary from node to node.

Ah, great. Thanks for the explanation.