Bitcoin Forum

I ve give a tsx order from Electrum with static fee 1 sat/b. after i see the low fee warning i ve rise fee to 70 sat/b static. after 24h its still unconfirmed. what should i do? how many days i need to wait for confirm or cancel?

honestly, it's impossible to say for certain...

you can get "some" idea by watching websites like https://mempool.space/ and https://jochen-hoenicke.de/queue/#BTC,24h,weight which give an overview of the current network conditions and transaction fees.

Unfortunately, the network is very busy right now... so you 70 sats/vbyte is  not even half what you need to have a chance of confirmation... 70 sats/vbyte is around 30 blocks from the tip. Assuming no new transactions are added that would take ~300 minutes or 6hrs... however new transactions will be added... so you're in for a long wait :-\

According to https://jochen-hoenicke.de/queue/#BTC,24h,weight, in the last 24 hours the fees never gone below 175 sat/b. For your Tx to get confirmed it needs 200+ sat/b which is crazy and I do not think I have seen such congestion in mempool before.

how many days it should be. weeks? months?

Mempool will likely be less congested tomorrow. Wait till tomorrow (Sunday), the mempool should be less congested, and likely the transaction will be confirmed.

I'm not so sure. I know things usually get better on Sundays, but I don't think we will see the mempool empty down as low as 70 sats/vbyte over this weekend. Hashrate has dropped acutely over the last few days, and we are currently lagging almost 70 blocks behind the 10 minute average for this difficulty epoch. We've only mined a single block in the last 2 hours. Combine this with the price pushing ATHs and the increased transaction volume that this always brings, the mempool is currently filling up more rather than emptying. A few hours ago 70 sats/vbyte was 20 MB from the tip. Now it is 30 MB and climbing.

If the hashrate doesn't pick back up and we continue to find blocks ~20% slower than predicted until the next difficulty readjustment, it could take weeks for us to clear down to 70 sats/vbyte.

Last time it was this bad was around the $20k ATH at the end of 2017.

i need to wait for a long time than thanks for you all

Looks like Jochen restarted his node which would explain the sudden drop and empty mempool between 19:00 - 19:30. I don't think we can't trust the site's estimates just yet because it's currently showing 5 vMBs of unconfirmed transactions in the 70 sat range. We are missing 25 vMBs or so from before the reboot. 

Lately, it has become a bit troublesome, he is purging at times transactions with fees lower than x and the graphics are misleading, I've completely switched to mempool.space it's more user-friendly and a bit more reliable. Also, I love the graphic of the size of the incoming transaction, of course, it doesn't help you predict anything more accurate but I prefer the look.

I assume it's also easier to understand for newbies, you see 5 blocks waiting, you see the minimum few to get in even if nobody send a new one is 167sat/b, you gave up and enjoy the weekend  ;D


It won't unless the mining in China restarts. We've below 30% right now with only 200k transactions in the last 24 hours, unfortunately, this is still less than what we have on a normal weekend so nope, at this pace we won't see even 100sat.
The other possibility might be that people would stop sending higher fees and wait but I don't see that happening either, Binance is sending 200sat/b transactions like there is no tomorrow and they're still getting deposits even with those fees.
https://blockchair.com/bitcoin/address/1NDyJtNTjmwk5xPNhjgAMu4HDHigtobu1s



 

Just choose "BTC" instead of "BTC (default mempool)" at the top. It switches to a node which has a much higher max size limit, and so shows all transactions without any being purged. It also did not restart earlier like the default node did, so there is no sudden drop in transactions or wait for them to be re-received.

I also like mempool.space for their visual representation of each block, the timing, and the fee range, but their graph just isn't as good. They need to implement a mouse over pop up with exact sizes at each fee band like Jochen's has.

Ugh....I do hope that doesn't happen.  There's some bitcoin I'd like to send relatively soon, and right now the network fees are prohibitive.  It's too bad none of those so-called free bitcoin accelerators work. 

Times like these, I wish some merchants accepted coins other than bitcoin.  If I wanted to buy a laptop from Newegg this weekend, for example, there would be absolutely no advantage to use bitcoin.  It'd be so much cheaper to use an altcoin like Dash (or take your pick)--or even fiat! 

So yeah, OP, you're going to have to be very patient or figure out a way to increase your fee if you can.  It sucks when bitcoin gets like this, but fortunately it isn't all that often.

ViaBTC works, but requires impeccable timing.

If you want to place a link to your transaction, we can try to help you with the ViaBTC accelerator, which has been proven to work if the fee criterion is met. In case you do not want to post a link publicly you can send me a link to a private message, and I will be happy to try to help - as Loyce says, the method works, you just need to be very precise in timing.

Have you tried to increase the fee?, electrum has an RBF feature to do that.

click unconfirmed tx then increase the fee button

https://i.postimg.cc/7h1wqn5H/1.jpg

https://i.postimg.cc/FF09bNDM/2.jpg

now its became LOCAL in my wallet.

What I know in the case that a transaction is labeled Local is that the transaction is not broadcast at all - it means that you prepared the transaction and saved it, but did not actually send it. In the quote part you have a solution to the problem, just note that the fee is quite high at the moment - over 200 sat/vbyte for the next block.

A local transaction is a transaction that only your wallet can see. It doesn't exist on the mempool. This usually happens when the user clicks on save instead of broadcast or when it's an unconfirmed transaction that has been dropped from the mempool (eg. If you receive a transaction then the sender cancels it, its status will change from unconfirmed to local on your Electrum).

@uaaeu, if you are not going to broadcast that local transaction, then you should remove it from your wallet history.

i removed it when i see. its removed and my money is back but when i checked it again it turns unconfirmed again why?

This transaction could save 47% on fees by upgrading to native SegWit-Bech32 or 35% by upgrading to SegWit-P2SH

is it possible to upgrade for this unconfirmed tsx to segWit-Bech32?

lock time: 679494

am i need to wait 679494 blocks if its unconfirmed?

No. Until block 679494. But you should not worry about it, it has already passed, last block was already 679711

No.
It's recommended to hold your coins in segwit addresses to pay lower fee when you make a transaction. As your fund is now in a legacy address (an address starting with 1), there is no way to benefit the discount.
From now on, try to use segwit addresses for holding your bitcoin.

There are two types of segwit addresses.
1. Native segwit (Bech32): addresses starting with bc1
2. Nested segwit (P2SH): addresses starting with 3*

*Just note that not all addresses starting with 3 are segwit. Multisig addresses start with 3 as well.

how many days should i wait for dropping from mempool if my tsx still unconfirmed

No. You have to create a brand new segwit wallet and move all your coins to it to take advantage of the lower fees segwit provides.

No. The locktime is the earliest block which can include your transaction. Since we have already passed block 679,494, your transaction is free to be included in a block.

Provided you do not rebroadcast your transaction, it will be removed from default mempools either when the mempool size limit is filled with transactions paying a higher fee and your transaction is purged from the bottom, or after 14 days.

have you broadcasted yet?.

since happen to local (clicked - advance feature fee), I am not sure you going to that.

https://i.postimg.cc/c1VYv7H7/Capture.jpg

after a sign, you should also click a broadcast button.

In contrary with the previous posts, your "unconfirmed" transaction turned "local" is because your selected server's node had purged your transaction from their mempool due to prioritizing txns with higher fee rates.
Then it returned to your wallet after either auto-connecting to a different server that has your transaction or it was re-accepted by their node.

70sat/vB is good enough IMO if you're not in a hurry. It's just because the average mempool is absurdly too high right now that a txn with good fee rate like that got stuck.
You can also try to accelerate it using ViaBTC's free accelerator (https://www.viabtc.com/tools/txaccelerator/), send it to them at exactly HH:00 in the clock.