Author

Topic: Blockchain.info transaction still not confirmed after 2 days (Read 257 times)

sr. member
Activity: 1372
Merit: 322
Address type does not affect the speed of confirmation but reduces the fee.
Blockchain.info (buggy wallet) uses legacy addresses and therefore higher fees (normal fee using that wallet need longer confirmation time.)
At the end, isn't both meaning the same? Less fee in segwit than Legacy means faster confirmation. Blockchain has no segwit address? I can't remember when I last used it.
legendary
Activity: 2170
Merit: 1427
Like I said, it uses a fee Blockchain.com thinks is high. But is it though? It may be, or maybe the mempool spikes as soon as you send the transaction and fees increase 2x, putting you down the line, etc...

If these bastards added Segwit and RBF they would allow the users to be more in control of their transactions and bump the fee when needed.

It sucks to see people keep using this despicable service, but they are so strongly positioned with their SEO that newbies automatically see blockchain.com pop up on top. The only positive aspect of this is that newbies aren't using a scam wallet, but still, it may not be a scam wallet, but still a trashy one where they don't allow people to transfer funds to a bc1 address.
legendary
Activity: 2702
Merit: 4002
Been using blockchain.info for a couple of years now and I've always done the standard fee that blockchain allows and all transactions have normally taken an hour, this one however is still not pending, currently 0/3
It seems that the user created this account for the purpose of this question but because you are using blockchain.info for several years, have you noticed that you are paying a higher fee than usual?
There are a lot of wallets that do not need much technical knowledge and which are much better than blockchain.info wallet.

I thought "priorized" uses the maximum fee for the faster transactions. Sender address was legacy in my case, which was the another reason of delayed cconfirmation. Thank you for breaking down it.
Address type does not affect the speed of confirmation but reduces the fee.
Blockchain.info (buggy wallet) uses legacy addresses and therefore higher fees (normal fee using that wallet need longer confirmation time.)
legendary
Activity: 2758
Merit: 6830
I thought "priorized" uses the maximum fee for the faster transactions. Sender address was legacy in my case, which was the another reason of delayed cconfirmation. Thank you for breaking down it.
There is no such thing as “maximum fee”; you could even send a transaction with a 2000 sat/byte fee right now. Like I said, it uses a fee Blockchain.com thinks is high. But is it though? It may be, or maybe the mempool spikes as soon as you send the transaction and fees increase 2x, putting you down the line, etc...
hero member
Activity: 1358
Merit: 851
Correct, in blockchain.com, you can choose option like as you referred. For faster confirmation, one can choose prioritized. However, it still is a mystery to me. I had a payment pending for more than 24 hours even though the sender said he choose prioritized.
Because “priorized” is just a label put by Blockchain.com for what their algorithm thinks is the best fee for the moment, which may be incorrect. It all depends on the mempool and the fee choosen. The network doesn’t see labels, only numbers. And if there are txs with fee numbers higher than yours, they will be picked up first.
I thought "priorized" uses the maximum fee for the faster transactions. Sender address was legacy in my case, which was the another reason of delayed cconfirmation. Thank you for breaking down it.
legendary
Activity: 2758
Merit: 6830
Correct, in blockchain.com, you can choose option like as you referred. For faster confirmation, one can choose prioritized. However, it still is a mystery to me. I had a payment pending for more than 24 hours even though the sender said he choose prioritized.
Because “priorized” is just a label put by Blockchain.com for what their algorithm thinks is the best fee for the moment, which may be incorrect. It all depends on the mempool and the fee choosen. The network doesn’t see labels, only numbers. And if there are txs with fee numbers higher than yours, they will be picked up first.
hero member
Activity: 1358
Merit: 851
IIRC blockchain.info always choose the lowest fees to make a transaction. My suggestion is, use another wallet with RBF support, so you can push your TX when it's required. That will save a lot of your time especially if you need fast confirmations.
I think you can choose between "Regular" and "economy" or "Prioritized".
Correct, in blockchain.com, you can choose option like as you referred. For faster confirmation, one can choose prioritized. However, it still is a mystery to me. I had a payment pending for more than 24 hours even though the sender said he choose prioritized.
legendary
Activity: 1946
Merit: 1427
IIRC blockchain.info always choose the lowest fees to make a transaction. My suggestion is, use another wallet with RBF support, so you can push your TX when it's required. That will save a lot of your time especially if you need fast confirmations.
I think you can choose between "Regular" and "economy" or "Prioritized".

But yeah, it'd be much better to switch considering they dont support bech32 adresses, and don't broadcast/sign with RBF sequences, which is just stupid for everyone involved.
legendary
Activity: 2170
Merit: 1789
IIRC blockchain.info always choose the lowest fees to make a transaction. My suggestion is, use another wallet with RBF support, so you can push your TX when it's required. That will save a lot of your time especially if you need fast confirmations.
legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
Thank you so much for the speedy replies Smiley

I'll just have to wait
It's now confirmed with 11 confirmations.

Next time, if you have no idea what to put in the fee rate, make 10sat/byte your minimum
(Higher for SegWit because some sites often have errors in computation of the fee with Segwit addresses).
Why? Some free accelerators like the one suggested above only accept TXIDs with fees higher than 10sat/byte  Wink
newbie
Activity: 2
Merit: 0
Thank you so much for the speedy replies Smiley

I'll just have to wait
legendary
Activity: 2800
Merit: 2736
Farewell LEO: o_e_l_e_o
The mempool is overloaded with transactions. So, you may need to wait few more days I guess.

Your tx has a 3 sat/byte fee and the mempool is currently confirming 50 sat/byte transactions. In the last 24 hours, it didn't even get into 6 sat/byte transactions due to a spike on the mempool

Two days ago I had this experience of sending coins using only 1 sat/Byte and it took only less than 20 mins but today I broadcasted a transaction for the same fee and it's showing 48.89 MB from tip which means it's gonna take long time. I don't mind however.

For the OP, if you are not in hurry then my best advise will be - to wait. I paid 1 sat/byte and your paid 3 sat/byte which means yours will be confirmed long before me. So, don't you worry 🤪
legendary
Activity: 2758
Merit: 6830
There isn't much anyone can do. Your tx has a 3 sat/byte fee and the mempool is currently confirming 50 sat/byte transactions. In the last 24 hours, it didn't even get into 6 sat/byte transactions due to a spike on the mempool[1].

All you can do is wait and maybe try ViaBTC's free accelerator (the ONLY real accelerator that works): https://pool.viabtc.com/tools

I also rebroadcasted your tx in multiple block explorers (not that this is going to change anything, but I know that many people will come here doing this and calling it an "acceleration" - which is NOT - so I did it anyway).

[1] https://jochen-hoenicke.de/queue/#0,24h
newbie
Activity: 2
Merit: 0
Hiya People,

Been using blockchain.info for a couple of years now and I've always done the standard fee that blockchain allows and all transactions have normally taken an hour, this one however is still not pending, currently 0/3

My transaction is

dfeea3249cd0db9be967fbcf02d72d2a09ce87e70630dbf358026eb68132c32e

Can anyone advise me what to do to speed this along?

Thank you
Jump to: