[SOLVED] 0 confirmations after 10 hours, 0.0001 tx fee, what's wrong?

[carajillu]

Hi guys, I've been pretty active lately sending and receiving BTC from my main address, but yesterday I sent a tx of 0.6 BTC with a regular fee of 0.0001 BTC and in 10 hours has not confirmed yet. Can anybody help? I'll put more fee next time, but I thought 0.0001 is the regular amount nowadays. Can anybody explain briefly how to calculate properly the tx fee?

The tx id is: https://blockchain.info/es/tx/0cf1e3ee87b1ec2c78ccff87e6dd0c286b5ad201d1e73ecedef01d8372147aea

Also...is it possible to help confirming manually? I'll send you 100k satoshis for the work

[1713999876]

1713999876

[1713999876]

1713999876

[1713999876]

1713999876

[1713999876]

1713999876

[funkydog]

PM user "macbook-air", he can do it for a fee.

[carajillu]

PM user "macbook-air", he can do it for a fee.

Thanks! I'll do it

[ranochigo]

Miners calculate the ranking of the transactions by BTC/KB. The lower it is, the lower the ranking it will be. Your transaction fee is 0.0001BTC and the size is 2947bytes, around 0.00003BTC/KB. The settings in the reference client indicates that fees below 0.00005BTC/kb will not get relayed unless the settings get changed. With lesser nodes willing to propagate your TX, not all miners would see it.

Next time you send a TX, make sure that you have a suitable fees/kb.

Macbook air is the owner of F2pool so you could try. He has done it before.

[carajillu]

Miners calculate the ranking of the transactions by BTC/KB. The lower it is, the lower the ranking it will be. Your transaction fee is 0.0001BTC and the size is 2947bytes, around 0.00003BTC/KB. The settings in the reference client indicates that fees below 0.00005BTC/kb will not get relayed unless the settings get changed. With lesser nodes willing to propagate your TX, not all miners would see it.

Next time you send a TX, make sure that you have a suitable fees/kb.

Macbook air is the owner of F2pool so you could try. He has done it before.

What is sad is that the tx was sent using blockchain.info online wallet...So their fee calculation system does not work correctly I guess

[ranochigo]

Miners calculate the ranking of the transactions by BTC/KB. The lower it is, the lower the ranking it will be. Your transaction fee is 0.0001BTC and the size is 2947bytes, around 0.00003BTC/KB. The settings in the reference client indicates that fees below 0.00005BTC/kb will not get relayed unless the settings get changed. With lesser nodes willing to propagate your TX, not all miners would see it.

Next time you send a TX, make sure that you have a suitable fees/kb.

Macbook air is the owner of F2pool so you could try. He has done it before.

What is sad is that the tx was sent using blockchain.info online wallet...So their fee calculation system does not work correctly I guess

Doesn't really make sense since you see the warning beside the estimated confirmation time.

At any rate, I would avoid Blockchain.info at all cost. I used to use it as my primary wallet but changed it sometime after since they are usually very buggy.

It appears that the blocks are close to filled at the moment hence it would take some time.

[medUSA]

Your tx has 16 inputs which made the tx nearly 3k in size, you should have used 0.0003 btc fee.

What is sad is that the tx was sent using blockchain.info online wallet...So their fee calculation system does not work correctly I guess

Blockchain.info wallet always warn you about fees, fee calculation system does work. You must have ignored their warning or sent custom tx. You have to wait for it to confirm, but network is busy, more than 7k tx in mempool. It's going to take a while.

[carajillu]

Well, I used mobile app to perform the tx and I don't remember getting any warning. Could be an app bug or could be that i just pressed OK :S Anyway, would be nice to have a tx including service somewhere, like macbook-air can do. A service in a pool (where for sure some blocks will be mined) were you can pay a fee and tell them your txId and make them include automatically in next block. If they implement it would be an extra BTC earnings for the pool operators.

[medUSA]

A service in a pool (where for sure some blocks will be mined) were you can pay a fee and tell them your txId and make them include automatically in next block. If they implement it would be an extra BTC earnings for the pool operators.

There are talks about changing the bitcoin protocol to allow adding fees to sent txs, or child-pay-for-parent type systems. We are not there yet, so for now, we need to place enough fees into txs before we send them. It's not difficult to get used to

[winspiral]

last week i had to wait 50 hours to see confirmations...
with same fees rate as usual...
it happened to me twice fot many many sendings.

[achow101_alt]

A service in a pool (where for sure some blocks will be mined) were you can pay a fee and tell them your txId and make them include automatically in next block. If they implement it would be an extra BTC earnings for the pool operators.

There are talks about changing the bitcoin protocol to allow adding fees to sent txs, or child-pay-for-parent type systems. We are not there yet, so for now, we need to place enough fees into txs before we send them. It's not difficult to get used to

Bitcoin Core 0.12 will support Opt-in RBF so that if you opted in then you can increase the fee by resending the transaction. Opting in involves having a different sequence number in the output.

[carajillu]

Yeah! It finally confirmed! I will include enough fees next time, lesson learnt and also learnt a lot about tx fees and bitcoin core also, so far so good.
At this point I support the idea of including in core the possibility of increase fees of an already sent tx, would really help users and also miners.

[nwfella]

Yeah! It finally confirmed! I will include enough fees next time, lesson learnt and also learnt a lot about tx fees and bitcoin core also, so far so good.
At this point I support the idea of including in core the possibility of increase fees of an already sent tx, would really help users and also miners.

Good deal.  Glad to hear your funds finally went through.  You might want to consider closing this thread out.

[Bitfirm]

that might happen pretty often for quite some time for quite many transactions now
blocksize problem is starting to show

[shorena]

that might happen pretty often for quite some time for quite many transactions now
blocksize problem is starting to show

The average block size is still only @0.75[1], the typical time to wait for a confirmation is if anything lower than it was for most of the year[2]. The cost per transaction is the lowest over the last 2 years[3].

Its not as dramatic as you try to make it.

[1] https://blockchain.info/charts/avg-block-size
[2] https://blockchain.info/charts/avg-confirmation-time
[3] https://blockchain.info/charts/cost-per-transaction?timespan=2year&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=