Topic: Blockchain.info bug? (Read 938 times)

It is only a temporary thing.  So just wait and it all works itself out.

so what happens if coins are 'stuck' and unconfirmed in a blockchain wallet, export the wallet to a nother client and then spend them?

And again now...

https://blockchain.info/tx/e50335a70d3990333b9f36dcf32e70be8bf8f2996dfb85af1eff23e08959ca31

This is exactly the same issue caused by not correctly handling an orphaned block.

Their orphaned block processing is FUBAR.

I also noticed that if you try to list the orphaned blocks here:

https://blockchain.info/orphaned-blocks

you get an error.

This may not be related but they cannot even list the orphaned blocks.

I suspect a code update was pushed out that has a bug in this area because they used to properly process orphaned blocks and now they do not.

Previously I posted some issues on Blockchain.info thread, but that was not solved either. Looks like their blockchain processor is failing to take the huge load on them. Here is another instance...

https://blockchain.info/tx/958150110f8a906619eaed09d6008f3aff0ffebc98cfd57eecbe203c4186a3df - Unconfirmed

https://helloblock.io/transactions/958150110f8a906619eaed09d6008f3aff0ffebc98cfd57eecbe203c4186a3df - 28 Confirmations

http://blockr.io/tx/info/958150110f8a906619eaed09d6008f3aff0ffebc98cfd57eecbe203c4186a3df - 28 Confirmations


As a lot of bitcoin businesses depends on their API till date, they should be a bit more careful on this behalf.

Hopefully piuk will respond here.

Looks like a real bug to me.  I cannot see why it is saying it is unconfirmed when it is in a block.

PM sent to piuk.

I see it now.  According to blockchain.info the transaction was included in a block that was orphaned:

https://blockchain.info/block-index/421582

With this hash:  00000000000000000591be5b8e4ec5fd6f94833c2490d59619faa6cdf55ddad8

However according to this:

https://blockr.io/block/info/303349

The transaction was also included into the main chain block with this hash:

0000000000000000634019c8795075690f4346035c49fa38e1385c7c5afc3490

So it looks like a bug at blockchain.info.  The transaction should be shown to have occured in the main chain block but for some reason the transaction is "stuck" showing that it only occured in the orphaned block.

Interestingly the main chain block in the blockchain.info database:

https://blockchain.info/block-index/417823

Does show the transaction just fine.  The transaction itself is of course confirmed.  The issue is that the transaction is stuck pointing to block-index 421582 when it should be pointing to block-index 417823 in the blockchain.info database.

ONE MORE THING:  It appears that all the transactions in the ophaned block (index 421582) are showing as unconfirmed but were in fact confirmed in the main chain block (index 417823), some examples:

https://blockchain.info/tx/8e50a3892324e11e0a5f548c73d7e6c24a5c701f6f27c277a2ef7fde370d3974
https://blockchain.info/tx/311dba51e7332426f68c77eac3c0968a2feb3c5dca29502a7fd97c14968ba1e8
https://blockchain.info/tx/ba5381ab56fbd1c58499ac349a2e6fad347e904283abbfcb6094bdc63a9bcdf4
https://blockchain.info/tx/e60150636b5df0cd503c8bd103e196439b02e09ae175c85359c329e3cf5e294e

etc.

This is cool.  Take a look at the "Reward from block" field in the "unconfirmed" yet spent coinbase transaction from the main chain block:

https://blockchain.info/tx/4d38b494f801bde014a0129e99f5ea8a2bfae54979351fc201f819ee74b69301

The blockchain.info database appears totally hosed.

It does look like a bug, and the tx did get included in block 303349.
https://blockexplorer.com/tx/fb064156b73e2835911f72aa252576212e185df9d0bf66eb4d09ea2bd999656b
https://blockr.io/tx/info/fb064156b73e2835911f72aa252576212e185df9d0bf66eb4d09ea2bd999656b

Hi!

What do you think about this transaction?

https://blockchain.info/tx/fb064156b73e2835911f72aa252576212e185df9d0bf66eb4d09ea2bd999656b

It says "unconfirmed transaction" and "0 confirmations" but "Included In Blocks: 303349 (2014-05-30 16:39:47 +6 minutes)" at the same time.

(screenshot: https://www.dropbox.com/s/k6ud3cr5ep8lp78/blockchaininfobug.png)