You can potentially expedite the transactions by sending the unconfirmed bitcoins to yourself with a fee that is high enough to be confirmed quickly. This is called CPFP (Child Pays For Parent).
I'm working with someone right now who's showing me how to set up this very thing using Electrum and my Ledger. If this works I'll come back and confirm that it does.
Thanks!
You're in the same situation as this guy:
Re: Bitcoin transaction pending for quite long,
it would take a very high transaction fee to CPFP it to 1mb-from-tip since there are 8 more parent transactions that are all unconfirmed with the same fee rate and vSize.
but at least you can bump that unconfirmed transaction group closer to the tip of the nodes' mempools.Example: All 8 unconfirmed parent transactions (
including your 2nd transaction) are all 166vBtes with 1699sat fee (
10sat/vB).
If you CPFP with 100sat/byte and that transaction have 166 vBytes size (
average).
The tx group will only have an effective fee rate of 20sat/vByte [30,192/1494=20], not enough for fast transaction at this moment.
That site must have been spending the unconfirmed change of the other clients' withdrawals creating a chain of unconfirmed transactions.
It's based from this: Your withdrawal transaction's input is the change of your other withdrawal transaction.
And if you perform CPFP to the first transaction in the OP (
35c1ff29f.....), it will affect the second transaction.
