You need to track back through all the Red U's... that is the full chain of unconfirmed parent transactions... until each and every one of those is confirmed, your transaction will not be able to be confirmed (or accelerated).
I think there are like 3 unconfirmed parents...
Just a quick tip: IF the dependance chain is "clean" (no double spends, no dust outputs, no child/parent transactions broadcasted in reverse order, no 0-fee tx's, no really weird situations), it should be in my mempool.
If it is, you can use this beta tool to look up the full chain:
https://www.mocacinno.com/showchain.php?txid=a871fc14eecbae818a99581af8eeb2cf0173875dd5ebe0a664ff459f1044b8d1In this case, you are correct (didn't doubt you in the first place, just wanted to give everybody a faster way to look up these chains)
Transaction a871fc14eecbae818a99581af8eeb2cf0173875dd5ebe0a664ff459f1044b8d1 depends on following transactions:
Array
(
- => a4f76f6c820e8ed7dab4ab09939d77993c7c7365ca13a56c544937791619d53c
[1] => f55049d3db713b7077bc3a0c7bc33fba22fe49121da8baf4dde78fb6c83a9d7a
[2] => ac9a7e825ddb43f2f26c5018edbba804a97944a882baa1b853f60c29d7b0f3db
)
Okay thanks for the tip @HCP for tracking back the red U's. So that means I cannot accelerate the ones with the red U's yet, and I finally understand. I have successfully accelerated the 1st parent
a4f76f6c820e8ed7dab4ab09939d77993c7c7365ca13a56c544937791619d53c with ViaBTC and now waiting for the next two to clear from the red U. I'm now learning a lot.
Also thank you @mocacinno for guiding me through this. Now I'm going to do the same for my upcoming payments later on. Will update this thread if I successfully received it till the last TXID.
