Quote from: abruzzy on January 16, 2018, 10:33:31 PM

Thanks for your reply!
I already tried that many times but i am getting an error message.

http://prntscr.com/i1ff7w

this is the transaction ID
7e5dcd4eaf2ebe4cadc238cc890f7e9a1e1180c022e40e54ca56897bee132427

I'm not sure about that error message. Do you have enough funds avaliable from the sending address in order to do the RBF - double spend.

Quote from: abruzzy on January 16, 2018, 11:52:04 PM

Quote from: BitMaxz on January 16, 2018, 11:39:15 PM

Did you tried to accelerate it or CPFP?
Try to push your transaction follow this method below

Quote from: BitMaxz on January 16, 2018, 11:27:46 PM

There are lots of ways to accelerate your transaction but if you are using electrum wallet this transaction should be rejected and you can start send again but need to increase the miners fee.. Try the CPFP(Child Pays For Parent) just send another bitcoin from your bitcoin address to other bitcoin address but make sure this time to increase the miners fee use the default fee here https://bitcoinfees.earn.com/ its enough to pay your new transaction and your old stuck transaction..
You can also try this method

1. First open go to blockchain.info copy paste your txid e055308422bdbbe0028151e238e0df4779f73679d1e749a6c3ced811225c6c8b
2. as you can see your transaction still not confirm now add ?format=hex to the url sample
https://blockchain.info/tx/e055308422bdbbe0028151e238e0df4779f73679d1e749a6c3ced811225c6c8b?format=hex
You can see the hex code.
3. copy the hex code and submit it to pushtx listed here https://en.bitcoin.it/wiki/Transaction_broadcasting

And hope that your transaction can be confirm..

Also try submit your transaction here https://pool.viabtc.com/tools/txaccelerator/ and here https://www.antpool.com/user/prioritiseTransaction.htm?m=savePrioritiseTx
Make sure you login first in antpool before you use that link and submit your unconfirmed transaction..

I heard the transaction should be rejected and back to my wallet !
But this is not happening after 11 days !

Under standard rules, it should be rejected after 21 days, however, sometimes it isn't.

If someone configures their mempool differently in their node then it may never stop being broadcast and you can still lose money doing it that way as your transaction can be re-broadcast by someone else if you don't spend the inputs for it.