first things first, a chain of unconfirmed transactions != double spending.
What you probably have read is that when your incoming transaction uses the outputs of an unconfirmed parent transaction, there is a risk the creator of the parent transaction double spends the input of the parent transaction, and every other transaction in the chain gets cancelled. This is true.
If you trust the person who is using unconfirmed unspent outputs to build new transactions, this does not HAVE to be a problem. However, it is true that your transaction can not be confirmed BEFORE all parent transactions of your transaction are confirmed (they can all be put in the same block tough, just not in an earlyer block).
What you probably have read is that when your incoming transaction uses the outputs of an unconfirmed parent transaction, there is a risk the creator of the parent transaction double spends the input of the parent transaction, and every other transaction in the chain gets cancelled. This is true.
If you trust the person who is using unconfirmed unspent outputs to build new transactions, this does not HAVE to be a problem. However, it is true that your transaction can not be confirmed BEFORE all parent transactions of your transaction are confirmed (they can all be put in the same block tough, just not in an earlyer block).
Thanks for the reply.
Any suggestions as to what, if anything I might be able to do to get things moving?
In order for you to fix your first transaction (9d9123565f2900f0ea3cd4e7aa6d16736243ac4728d285bec6441e4eb67e2a22), transaction 3f9d89be1024c292c0cc832a41b25b458e834fe9037d7d3b758c54628eb380be has to be confirmed first.
Can you give a bit of background information?
Did you create these transactions? Which wallet(s) did you use to send/receive? Which addresses are yours?
Thanks for the reply.
Yes, I created both transactions using Electrum 2.8.2.
Not quite sure which addresses are mine, sorry.
No problem... I just noticed that 3f9d89be1024c292c0cc832a41b25b458e834fe9037d7d3b758c54628eb380be is opt-in rbf... This is great
. You can use electrum to bump the fee... Just right click on the pending transaction and chose "increase fee" .Don't enable the checkbox "finalise"!The second transaction is using an output from the first transaction, so if you RBF the first transaction, the second one will most likely be cancelled and will probably have to be recreated.
