It is saying by the confirmation time: This transaction spends an input which is unconfirmed. Any ideas people?
This is a bug at ZenMiner.
Only they can fix it.
It appears that they might have been hit by the transaction malleability bug?
Specifically:
The transaction that pays you:
64f1e7a2b2b53878621d3b29d1f92d39de97e89b2847a2a9f9ad0a77184615e4
Is attempting to spend an unconfirmed output received by ZenMiner with transaction:
f574cd019087367f1723cb29d461b66889e681c0275f06b43f8e8904c28d0486
That transaction is attempting to spend an unconfirmed output received with transaction:
a2b973d0c41d7c77550eddd3fb50fcf3229414ce6d878760a0a5d2263f1e3aa0
That transaction is attempting to spend an unconfirmed output received with transaction:
567c2f500777d869e23f7b6bdc9ecaa1d1bbab8bef60434a0d3d8827fbe224cb
That transaction is attempting to spend an unconfirmed output received with transaction:
0428c64542552c53b4bd0851e5653e28a4b182d602cd560ec6bb8ef40ed28e76
That transaction is attempting to spend an unconfirmed output received with transaction:
cfa4730fd6a569a94ef5db8a48cb073d14d02d07a53ab6fc65c7062bf6e4b8d6
That transaction is attempting to spend an unconfirmed output received with transaction:
11b5e614f300a303563095de92b7c6771901c9e8ea2477fdb71e7d3a77e13e61
That transaction is attempting to spend an unconfirmed output received with transaction:
b691fe6d870a4f9e62184eebcd548629d4e710b748232f8986c1291d30f099b8
That transaction is attempting to spend an unconfirmed output received with transaction:
59e1151dd81aaaa8691ed83a30a7c42105e1d4beecdaacc2272d07aee2a707ae
That transaction is unconfirmed because there is another identical transaction with a different hash that has already spent the output and which has already been confirmed:
62e2055b81aa7efc9650e941cd49c7fcf0f484fca108ca56630527b2b92ad4a9
They are both attempting to spend the confirmed output from transaction:
eb7cad0d1d9b732402fd81b3b96e7236728ee4fd87cd38512f52ca76e2863308
So, due to transaction malleability, there are two identical transactions with different transaction IDs.
One is confirmed:
62e2055b81aa7efc9650e941cd49c7fcf0f484fca108ca56630527b2b92ad4a9
The other is unconfirmed (and will never confirm):
59e1151dd81aaaa8691ed83a30a7c42105e1d4beecdaacc2272d07aee2a707ae
Because of this, the transaction that was sent to you:
64f1e7a2b2b53878621d3b29d1f92d39de97e89b2847a2a9f9ad0a77184615e4
can never confirm.
ZenMiner needs to fix the problem in their system that is attempting to spend unconfirmed outputs and then they need to send you a new transaction.