Author

Topic: Blockchain.info - Confirmations takes AGES! (Read 1234 times)

staff
Activity: 3458
Merit: 6793
Just writing some code
February 07, 2017, 01:15:00 PM
#8
It's not blockchain.info's fault.
The low fee is entirely blockchain.info's fault. They have something in their software which limits the maximum fee to be 65 satoshis/byte, thus making any transactions made with their wallet have a low transaction fee.

OP, You have a few options here. You can wait and hope it confirms, wait for the transaction to be "forgotten" by the network, or ask a miner to confirm it for you.

For the third option, you can contact the users Quickseller and macbook-air.

Unfortunately you will not be able to attempt a double spend with a transaction that pays a higher tx fee. Blockchain.info does not provide the advanced functionality necessary to do that.



Nothing AFAIK, it's even costing the money, because they won't earn as much on TX fees. So I guess they're doing it just out of niceness to the Bitcoin community. And maybe to promote their pool and BU a little Smiley
I think they are trying doing this as a PR thing to promote their pool and BU.
sr. member
Activity: 462
Merit: 250
February 07, 2017, 12:16:06 PM
#7
Try ViaBTC tx accelerator to confirm the transcation. It is a very useful tool for confirming tx with a small fee for free. TX will get confirmed when you submit txid there and they mine a block.

Why do they provide this free service? What's in it for them?
Nothing AFAIK, it's even costing the money, because they won't earn as much on TX fees. So I guess they're doing it just out of niceness to the Bitcoin community. And maybe to promote their pool and BU a little Smiley
legendary
Activity: 3556
Merit: 9709
#1 VIP Crypto Casino
February 07, 2017, 09:27:00 AM
#6
Try ViaBTC tx accelerator to confirm the transcation. It is a very useful tool for confirming tx with a small fee for free. TX will get confirmed when you submit txid there and they mine a block.

Why do they provide this free service? What's in it for them?
hero member
Activity: 840
Merit: 508
Make winning bets on sports with Sportsbet.io!
February 07, 2017, 01:19:59 AM
#5
Try ViaBTC tx accelerator to confirm the transcation. It is a very useful tool for confirming tx with a small fee for free. TX will get confirmed when you submit txid there and they mine a block.
sr. member
Activity: 966
Merit: 342
February 07, 2017, 01:08:51 AM
#4
Another link to show how transaction fee and transaction time correlates.

https://bitcoinfees.21.co
sr. member
Activity: 966
Merit: 342
February 06, 2017, 10:58:27 AM
#3
It's very busy at the network right now: https://blockchain.info/unconfirmed-transactions
At the time I wrote this there were over 45000 unconfirmed transactions, still growing.

For a small payment I received over 2 hours ago, there are still no confirmations, although there is enough on transaction fee.

And ofcourse, when you send it with just a small transaction fee, it will take longer then with a good transaction fee.

Edit:  now there are over 43000 unconfirmed transactions, but growing again (5 minutes later...)
sr. member
Activity: 462
Merit: 250
February 06, 2017, 10:55:53 AM
#2
It's not blockchain.info's fault. The fee you sent with the transaction was probably too small, it should be atleast 100 sats/byte if you want your tx to confirm in the next few blocks (https://bitcoinfees.21.co). You can try accelerating your transaction with ViaBTC (https://www.viabtc.com/tools/txaccelerator/) which means they'll confirm your transaction for you if they find a block. Except for that it's easiest just to wait it out, and make sure to pay a higher fee next time.

EDIT: Apparently blockchain.info limits their fee to 65 sats/byte so it is their fault. You'll need to get a different wallet if you want fast confirmation times.
newbie
Activity: 238
Merit: 0
February 06, 2017, 10:45:03 AM
#1
In the last two days I noticed it takes ages before my payments I send from my Blockchain.info wallet get confirmations.

Are there more people experiencing this problem?
Any idea what could be causing this?
Jump to: