Quote from: mithrandi on May 22, 2013, 05:00:29 PM

Quote from: astrolabe on May 22, 2013, 04:39:29 PM

The last unblocked transaction in the chain has 15 confirmations. https://blockchain.info/tx/618364652674551068cff5ce6a9b3889a6836c662c0f28c69c015e12ec6b6a6e

Is it out of the question that blockchain info has a bug?

The next transaction in the chain is this one: https://blockchain.info/tx-index/74252194

One of the inputs to that transaction is https://blockchain.info/tx-index/74245888/0 which is still unconfirmed.

Quote from: vortex1878 on May 22, 2013, 04:58:04 PM

Quote from: vortex1878 on May 22, 2013, 04:21:48 PM

Could this have to do with the bug in bitcoind that caused invalid blocks being generated?

I believe there was a fix for that only yesterday. And maybe ASICMiner have not yet applied that bugfix.

Could somebody who is not a n00b like me please answer my question?

I don't see anything to suggest that this is a problem with invalid blocks, it's just a matter of unconfirmed transactions being used as inputs for other transactions.

Interesting, I have never seen that done before... I knew SOMETHING was up... just not what. If you send me an address I will gladly tip you.