.:::: STUCK BTC TRANSACTION ::::. | Bitcointalksearch.org

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: ashrafohm1 on December 23, 2020, 04:01:22 AM

Looking at the screenshot... you still have 0.00622436 BTC (~6.22436mBTC) remaining in the wallet after the "unconfirmed transaction". You should, theoretically, be able to use this, along with the change from the "unconfirmed transaction" in a "Child Pays For Parent" transaction.

However, based on the info from your previous posts, due to your wallet using Legacy addresses, the total size, across both the unconfirmed and the CPFP transactions, would be at least 4100 bytes... at a rate of 100 sats/byte (which should hopefully get a confirmation within a few hours), you would be paying a total fee of ~0.00410000 BTC in fees!!?! Shocked

You could "gamble" and try using 50 sats/byte (currently around 4-5 blocks from the Tip) and mark the CPFP transaction as "RBF enabled"... that way if it is still taking too long, you could bump the fee later.

This case is the perfect illustration of:

1. Why users should seriously consider moving to SegWit (to reduce total transaction sizes and therefore reduce total fees)

and

2. Why users should consolidate UTXOs in their wallets when fees are at low levels. ie. Only using 1 or 2 legacy inputs to a transaction (instead of 26!!?! Shocked

), drastically reduces the overall transaction size, which drastically reduces the total fees required.

o_e_l_e_o

legendary

Activity: 2268

Merit: 18711

Quote from: ashrafohm1 on December 23, 2020, 04:03:10 AM

waiting long time, infinite time?

Long time, maybe. Infinite time, no.

If you do not re-broadcast your transaction, then there are two main ways it can drop out of the mempool without being confirmed. Firstly, it can be pushed out the bottom of the mempool when the node reaches its maximum mempool size. By default this is 300 MB, but nodes are free to change this. At the moment the mempool is around 50 MB, so this method is unlikely. Secondly, it can be dropped from the mempool when it reaches the expiry time. By default this is 336 hours (14 days), but again nodes are free to change this. Given that your transaction has now been unconfirmed for 9-10 days, then in a few more days it should drop from most nodes and you can try again with a higher fee, which you will need to include from other inputs (or use the same inputs but send less to the recipient).

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: ashrafohm1 on December 23, 2020, 04:03:10 AM

Quote from: nc50lc on December 22, 2020, 10:05:52 PM

-snip-
All I can say is, there's no other way to increase the fee since it's not marked as "replaceable" (RBF)
and the change is too small to do a reasonable CPFP unless you have other available coins (UTXO) to spend.

Thanks for your effort sir, but in the end what do u think, waiting long time, infinite time?

Not really, it usually clears within a week but this time, the "low-mempool-season" only took a few from 1sat/B transactions probably because of the bull run plus the strangely slow block rate this past few days.
If you're lucky it could be mined by Saturday or Sunday.

As I mentioned above, if you have another UTXO in your Electrum, open 'coins' tab (View->Show Coins) aside from that transaction's change, you can do a manual CPFP by using coin control.
CTRL+Left Click to multi-select the coin(s) you want to use then right click and select "spend" (don't forget to add the stuck txn's change as well),
there'll be an info below about the coins you've selected; finally create a transaction using the send tab with your own address as the recipient.
Set the fee considerably high because the parent's size is too high, at best, that could set the total fee rate of the parent+child higher than 2sat/B.
But I'd suggest you to just wait it out.

Lastly, read the posts above about bitcoins denomination.

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: nc50lc on December 22, 2020, 10:05:52 PM

Based from one of your recently posted screenshot, this must be your stuck transaction: e804e46637880a09b2c881d8101aecb87744f7923d18677e2d66157040490997

All I can say is, there's no other way to increase the fee since it's not marked as "replaceable" (RBF)
and the change is too small to do a reasonable CPFP unless you have other available coins (UTXO) to spend.

Thanks for your effort sir, but in the end what do u think, waiting long time, infinite time?

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: bob123 on December 22, 2020, 11:02:11 AM

Quote from: ashrafohm1 on December 22, 2020, 07:25:05 AM

and yes, I'm using forums since 2016 this is the first time I get a comment on my main thread formatting

Well, then someone should have commented way earlier.

It kind of hurts to read the OP. I don't get why anyone would decide to center the text while also using a huge font when asking a question.

Either way.. Your transaction has the RBF flag set.
This means you can replace it with a transaction paying a higher fee. Just go to 'History', choose the transaction, right click -> 'Bump Fee'.

Please note that RBF and CPFP is not the same.

seems that thread formatting causes problem to u guys more than the main topic itself .. lol

well, no bumb fee or rbf option exist

https://postimg.cc/1VHVdnSm

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: ashrafohm1 on December 22, 2020, 07:17:45 AM

If I'm not wrong this means the fees is around 920$

as it gives me error message "max fee exceeded" when I press OK

You are wrong... your Electrum is set to mBTC... ie. milliBTC... the fee being shown is 0.0803 mBTC = 0.00008030 BTC... or around US$2 Wink

Also, you're most likely getting the weird "max fee exceeded" error message because you simply don't have enough balance in your wallet to be creating the CPFP payment... hence why it is showing a negative(!!?! Shocked

) output amount of -0.02195 mBTC... you can't generate a negative amount! Tongue

To avoid confusion in the future, you might want to go into the Electrum settings and change the base Unit to "BTC" ("Tools" -> "Preferences" -> "General" -> "Base Unit")

At this point in time, I don't think there is anything you can do to push this payment through... it's just going to have to wait until the mempool empties out and 1 sat/byte transactions start getting include in blocks. This could, potentially, take days. Undecided

Perhaps over the Christmas holiday period while people are "busy" with family and real world stuff etc, it might clear out. Huh

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Based from one of your recently posted screenshot, this must be your stuck transaction: e804e46637880a09b2c881d8101aecb87744f7923d18677e2d66157040490997

All I can say is, there's no other way to increase the fee since it's not marked as "replaceable" (RBF)
and the change is too small to do a reasonable CPFP unless you have other available coins (UTXO) to spend.

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: ashrafohm1 on December 22, 2020, 07:25:05 AM

and yes, I'm using forums since 2016 this is the first time I get a comment on my main thread formatting

Well, then someone should have commented way earlier.

It kind of hurts to read the OP. I don't get why anyone would decide to center the text while also using a huge font when asking a question.

Either way.. Your transaction has the RBF flag set.
This means you can replace it with a transaction paying a higher fee. Just go to 'History', choose the transaction, right click -> 'Bump Fee'.

Please note that RBF and CPFP is not the same.

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Quote from: ashrafohm1 on December 22, 2020, 07:17:45 AM

If I'm not wrong this means the fees is around 920$
https://i.postimg.cc/J4cQZZ5g/Capture.jpg
as it gives me error message "max fee exceeded" when I press OK
if I set fee manually to 0.001 instead of 0.04 it shows fee is 0.5 sat/byte !
https://postimg.cc/MMwPs09Y

and it took too long not couple of days almost a week and didn't reach my seller yet !

he's pushing me Sad

The problem is that the size of your initial transaction is exceedingly big and it isn't helped by the fact that the transaction is sent from a legacy address. In the first picture, your denomination is mBTC(0.001BTC) and thus it's 0.00008BTC for both transaction and 0.00004BTC for your CPFP transaction.

I think your inputs amount is very small and there isn't enough left to spare for the fees and that's why it's giving the error. You can see that the input amount is only 0.01909mBTC which is very much smaller than the fees you are paying.

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: ranochigo on December 21, 2020, 10:38:39 PM

Quote from: ashrafohm1 on December 21, 2020, 09:10:17 PM

Thanks a lot for help, but what do u mean by high cost of fees now, is that for the wallet policy or for the current traffic ?

The number of transactions in the mempool has dipped for quite a bit. I don't think 1sat/byte transactions would confirm anytime soon so it'll help if you could import your wallet into Electrum and spend the change using a higher fee, back to your own wallet. You can do this by right clicking the unconfirmed transaction in Electrum and pressing child pay for parent.

check reply #11

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: bill gator on December 21, 2020, 09:51:58 PM

Quote from: ashrafohm1 on December 21, 2020, 02:11:41 AM

I have a stuck transaction for around a week

I set the fees to 1 sat/byte

I don't know if this is unique to me, but there's something about giant, emboldened and double-spaced text that really comes off rude. I honestly mean that in the most polite way possible; I'm nobody to tell someone how to conduct themselves, but it might be better received if you stick to the default text.

Unless you're just overly compassionate to those with poor eyesight. That I can understand!

Am I wrong in remembering that transactions get "cancelled" if they aren't confirmed by the network within a certain timeframe? It would just end up back in your own wallet and you can try again.

Actually 99% of threads are written in similar format, nobody makes his thread in the default format .. lol

and you double your space while typing your own reply for eye relaxation

also I'm a member in too many forums, this forum uses too old template that makes the text really to small and long to be easy to read

and yes, I'm using forums since 2016 this is the first time I get a comment on my main thread formatting

about cancelation yes there must be a solution by the time it won't be stuck forever but I'm just in a hurry cause the seller is pushing me, thanks.

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: Chikito on December 21, 2020, 09:39:01 PM

Quote from: ashrafohm1 on December 21, 2020, 09:10:17 PM

Thanks a lot for help, but what do u mean by high cost of fees now, is that for the wallet policy or for the current traffic ?

It's not about the wallet but the current traffic of bitcoin network. your TXID also failed, you inputted the wrong number, we can't check it.

You do not worry also, the recipient will receive his Bitcoin but maybe need a couple of days.

If I'm not wrong this means the fees is around 920$
https://i.postimg.cc/J4cQZZ5g/Capture.jpg
as it gives me error message "max fee exceeded" when I press OK
if I set fee manually to 0.001 instead of 0.04 it shows fee is 0.5 sat/byte !
https://postimg.cc/MMwPs09Y

and it took too long not couple of days almost a week and didn't reach my seller yet !

he's pushing me Sad

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: bill gator on December 21, 2020, 09:51:58 PM

Am I wrong in remembering that transactions get "cancelled" if they aren't confirmed by the network within a certain timeframe? It would just end up back in your own wallet and you can try again.

No, you're alright, that's based from nodes' default behavior which will drop unconfirmed txns from their mempool after 14-days (average) of staying.
For the "back to the owner's wallet", it'll look like it was never sent out after the transaction was removed unless the wallet stored a copy of it (like Bitcoin Core & Electrum, but it's simple to remove txns that were dropped from the mempools).

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Quote from: ashrafohm1 on December 21, 2020, 09:10:17 PM

Thanks a lot for help, but what do u mean by high cost of fees now, is that for the wallet policy or for the current traffic ?

The number of transactions in the mempool has dipped for quite a bit. I don't think 1sat/byte transactions would confirm anytime soon so it'll help if you could import your wallet into Electrum and spend the change using a higher fee, back to your own wallet. You can do this by right clicking the unconfirmed transaction in Electrum and pressing child pay for parent.

bill gator

legendary

Activity: 1372

Merit: 1123

Quote from: ashrafohm1 on December 21, 2020, 02:11:41 AM

I have a stuck transaction for around a week

I set the fees to 1 sat/byte

I don't know if this is unique to me, but there's something about giant, emboldened and double-spaced text that really comes off rude. I honestly mean that in the most polite way possible; I'm nobody to tell someone how to conduct themselves, but it might be better received if you stick to the default text.

Unless you're just overly compassionate to those with poor eyesight. That I can understand!

Am I wrong in remembering that transactions get "cancelled" if they aren't confirmed by the network within a certain timeframe? It would just end up back in your own wallet and you can try again.

Chikito

legendary

Activity: 2366

Merit: 2054

Quote from: ashrafohm1 on December 21, 2020, 09:10:17 PM

Thanks a lot for help, but what do u mean by high cost of fees now, is that for the wallet policy or for the current traffic ?

It's not about the wallet but the current traffic of bitcoin network. your TXID also failed, you inputted the wrong number, we can't check it.

You do not worry also, the recipient will receive his Bitcoin but maybe need a couple of days.

ashrafohm1

copper member

Activity: 53

Merit: 0

Quote from: HCP on December 21, 2020, 02:49:36 PM

Blockchain wallet may not allow for easy CPFP payments... but you could import your wallet into Electrum using your 12 word backup phrase from Blockchain.com and by using the "BIP39 Seed" option when creating the wallet in Electrum ("Standard Wallet" -> "I already have a seed" -> click "Options" button, tick "BIP39 Seed")

This would allow you to use the coin-control features to spend the change from your transaction and create a "Child Pays For Parent" (CPFP) transaction that might be able to get your transaction confirmed sooner.

The issue is that the fees have spiked to quite a high level again (100+ sats/vbyte)... so it's going to be a costly exercise. Undecided

Thanks a lot for help, but what do u mean by high cost of fees now, is that for the wallet policy or for the current traffic ?

HCP

legendary

Activity: 2086

Merit: 4361

Blockchain wallet may not allow for easy CPFP payments... but you could import your wallet into Electrum using your 12 word backup phrase from Blockchain.com and by using the "BIP39 Seed" option when creating the wallet in Electrum ("Standard Wallet" -> "I already have a seed" -> click "Options" button, tick "BIP39 Seed")

This would allow you to use the coin-control features to spend the change from your transaction and create a "Child Pays For Parent" (CPFP) transaction that might be able to get your transaction confirmed sooner.

The issue is that the fees have spiked to quite a high level again (100+ sats/vbyte)... so it's going to be a costly exercise. Undecided

sheenshane

legendary

Activity: 2492

Merit: 1232

Since you're using a Blockchain wallet, there's nothing you can do is wait for it when it will be confirmed. Your wallet used didn't even support Child Pays for Parent (CPFP) or even the double spend with a higher fee or Replace by Fee (RBF), as mentioned above.

Paying 1 sat is quite low and as we see on the Memory Pool (Mempool) through this site it becomes congested lately that has heavy traffic. If you noticed the color-coding on the chart, the color blue is represented as a 1-10 sats level transaction, you get probably stuck if you will not check the unconfirmed status transactions on the mempool.

Next time, learn to have a minimum transaction and regularly check the mempool. If you are in hurry, use a large fee, but if not, there's nothing to worry about to wait a longer time because your bitcoin is safe in the recipient wallet as long it is correct. Therefore, I advise you just to wait patiently.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

If you own any of the recipient addresses of the transaction (it can be even for the change), you can try to do CPFP, meaning to spend the unconfirmed funds from that address with an overly generous fee.
Of course, in order to do that you'll need a proper wallet, I am not convinced that blockchain wallet allows you choose where to spend from and also I don't know if it allows to spend unconfirmed funds.
One easy choice may be Electrum, but then you have to take care of safety measures, like verifying its signature before installing.

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Can you provide the full TXID?

1sat/byte is quite low considering that the mempool has spiked just now. ViaBTC requires about 10sat/byte if I'm not wrong so you can't push your transaction using their utility. The only thing you can do is to wait for the transaction to be confirmed because AFAIK, Blockchain.com doesn't offer RBF.

ashrafohm1

copper member

Activity: 53

Merit: 0

I have a stuck transaction for around a week

I set the fees to 1 sat/byte

Amount 260$ sent by blockchain wallet

I need anyway to release them

All accelerators asks for fees more expensive than the stuck amount

Viabtc.com show this message when I try to use their service: sorry your TXID doesn’t exist

Topic: .:::: STUCK BTC TRANSACTION ::::. (Read 351 times)