Unconfirmed transaction b/c of low fee, tried to do a CPFP no luck..

[ACRutten]

Basically, I was using Multibit but it kept glitching on me and randomly showing parts of my old balance as unconfirmed. So, I decided I wanted to switch wallets and went with Electrum. I was overly excited about the new wallet and hit the empty wallet button without truly thinking out the fees. Electrum immediately alerted me about the low fee. I did a tiny bit of research and found out Electrum could do the child pays for parent thing so I decided to give that a try. I did it and it's estimate says next block but that was hours ago so I may have done something wrong. I also tried to run the second transaction through TX accelerator over at viabtc but I guess that didn't help either.

Here's the first transaction..
 
37ccc18695eb5dc1bd3fd7c278accd289478296755996da1e28a4d21b821c104

..and here's the second..

6ac36c7fa027b1b157d37214fb06d63c2269df4379e3e759ce242c0a7277678c

Any help or information is greatly appreciated.

[1715037088]

1715037088

[1715037088]

1715037088

[1715037088]

1715037088

[AT101ET]

I don't think you did anything wrong. AFAIK the low fee is still the reason to blame for it showing up as unconfirmed. I would say just wait a bit longer until it eventually gets picked up. I once had to wait over 23 hours for a transaction to confirm.
On the bright side, at least you can now personally relate to the ongoing BTC transaction time dilemma 

[ACRutten]

Still, it seems strange to me that Electrum says that the second transaction should be included in the next block as well as looking it up in the mempool. I thought paying extra would help but it's still just marinating there in it's unconfirmed saddness.

[kolloh]

Usually the larger fee on the child will help the parent transaction confirm. But the original transaction only had a fee of 3 sat/byte and the transaction is quite big ( 21,715 bytes ) which may be causing some miners to ignore it even with the larger fee child.

I'm guessing this will still confirm due to the child transaction but will take some more time. Unfortunately, the first transaction's fee is too low to accelerate the transaction with ViaBTC as well.

[pooya87]

when you do a CPFP you need to pay for both transactions, in your first you have 0.00066 and in your second you have 0.0065721 and your total size is 21715 (bytes)+191 (bytes)
21,906 b * 180 s/b = 3,943,080 s (0.03943080BTC) which is smaller than 0.0072321BTC (your current total fee)

wait so that maybe it gets a confirmation or contact this guy and see how he can help you: https://bitcointalk.org/index.php?action=pm;sa=send;u=358020

[ACRutten]

The transaction finally went through over night so I guess CPFP thing actually worked. I seriously thought it was going to be in limbo for days. Still, I've checked use dynamic fees in electrum and I'm going to triple check the fees before I send out any other transactions.