<p>display bug on blockchain.info, they display the time that is in the block header, but since the time in the block header is allowed to be 2 hours off (and sometimes is because of performance tricks the pools do). </p>

<p><a href="https://www.blocktrail.com/BTC/address/1BacceeNmQzGFm11QwKdqmXA1wvnoHvaAv/transactions" rel="nofollow">https://www.blocktrail.com/BTC/address/1BacceeNmQzGFm11QwKdqmXA1wvnoHvaAv/transactions</a> shows them in the right order </p>

CC BY-SA 3.0
2015-01-26T19:02:23.413Z
2015-01-26T19:02:23.413Z
Ruben de Vries
<p>That's an interesting find! The transaction that created the output was in block 274227. The transaction that spent the output was 6 blocks later, 274233. So it's perfectly valid on the bitcoin network even though blockchain.info seems to have a glitch in the times they are reporting.</p>

<p>If they are basing the received time of the transaction at all on the time of the block it was included in, then you should know that the time recorded in bitcoin blocks can be a little off sometimes. See <a href="https://bitcoin.stackexchange.com/questions/915/why-dont-the-timestamps-in-the-block-chain-always-increase">Why don&#39;t the timestamps in the block chain always increase?</a>. Although, this doesn't appear to be what they are doing since they report two separate times, one for when the transaction was received and one for the time of the block.</p>

<p>Blockchain.info's API, Wallets, and Block Explorer are not known for being the most robust. They have started a bug bounty program, though: <a href="https://www.crowdcurity.com/blockchain-info" rel="nofollow noreferrer">https://www.crowdcurity.com/blockchain-info</a>. </p>

CC BY-SA 3.0
2015-01-24T21:15:52.303Z
2015-01-24T21:15:52.303Z
2017-04-13T12:47:36.707Z
morsecoder
<p>When browsing the blockchain.info I came across <a href="https://blockchain.info/address/1BacceeNmQzGFm11QwKdqmXA1wvnoHvaAv" rel="nofollow">this address</a>. It seemed peculiar to me, that the amount of 0.6 BTCs has allegedly been spend before received. </p>

<p>Is it because the "receiving transaction" somehow occurred in a side-chain and has only afterwards been merged into the Blockchain? Or what other explanations might there be for this behavior?</p>

<blockchain.info><sidechains>
Bitcoin spend before received
Juergen
# Bitcoin spend before received

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

When browsing the blockchain.info I came across [this address](https://blockchain.info/address/1BacceeNmQzGFm11QwKdqmXA1wvnoHvaAv). It seemed peculiar to me, that the amount of 0.6 BTCs has allegedly been spend before received.

Is it because the "receiving transaction" somehow occurred in a side-chain and has only afterwards been merged into the Blockchain? Or what other explanations might there be for this behavior?

**Tags:** blockchain.info, sidechains


---

## 2 answers

### Answer by username_2 on 2015-01-24. Score: 4 | Accepted answer

That's an interesting find! The transaction that created the output was in block 274227. The transaction that spent the output was 6 blocks later, 274233. So it's perfectly valid on the bitcoin network even though blockchain.info seems to have a glitch in the times they are reporting.

If they are basing the received time of the transaction at all on the time of the block it was included in, then you should know that the time recorded in bitcoin blocks can be a little off sometimes. See [Why don't the timestamps in the block chain always increase?](https://bitcoin.stackexchange.com/questions/915/why-dont-the-timestamps-in-the-block-chain-always-increase). Although, this doesn't appear to be what they are doing since they report two separate times, one for when the transaction was received and one for the time of the block.

Blockchain.info's API, Wallets, and Block Explorer are not known for being the most robust. They have started a bug bounty program, though: <https://www.crowdcurity.com/blockchain-info>.


---

### Answer by username_1 on 2015-01-26. Score: 1

display bug on blockchain.info, they display the time that is in the block header, but since the time in the block header is allowed to be 2 hours off (and sometimes is because of performance tricks the pools do).

<https://www.blocktrail.com/BTC/address/1BacceeNmQzGFm11QwKdqmXA1wvnoHvaAv/transactions> shows them in the right order


---

