The next transaction in the chain is this one:
https://blockchain.info/tx-index/74252194One of the inputs to that transaction is
https://blockchain.info/tx-index/74245888/0 which is still unconfirmed.
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.