Submitted to viabtc. The problem should be fixed when they mine their next block. If its not done by the time i get to the office, i'll also push it to antpool.
Just wanted to say amazing community here! I think the parent transaction is the problem. Thank you again and I look forward to working with you
You are correct,
fc99fe6e426fb98a5f8ae03ca5720998db5267b16c29c834c50ddff75043d00a is using outputs of fd7db6ff3150fd9c31d488bfcdfc5d0dc8faf222b4516137e0442c5ec62e3aa6, fd7db6ff3150fd9c31d488bfcdfc5d0dc8faf222b4516137e0442c5ec62e3aa6 has insufficient fees so it usually won't be added to a miner's block.
If fd7db6ff3150fd9c31d488bfcdfc5d0dc8faf222b4516137e0442c5ec62e3aa6is added to a block , fc99fe6e426fb98a5f8ae03ca5720998db5267b16c29c834c50ddff75043d00a will be confirmed shortly.
I added fc99fe6e426fb98a5f8ae03ca5720998db5267b16c29c834c50ddff75043d00a to the queue of both viabtc and antpool (just a couple miniutes ago). So if either of those pools mines their next block, fc99fe6e426fb98a5f8ae03ca5720998db5267b16c29c834c50ddff75043d00a should be in there... No guarantees tough, but it should be allright in a couple of hours!