I have 2 that have been suck half a day. I actually paid a higher transaction fee and they usually process right away...
Using Bitcoin Core version v0.11.2 (64-bit)
Status: 0/unconfirmed
Date: 2/28/2016 15:05
To: 1Fhif5KqJUTA5SU8NbVVcyNUVdWcYx7AdQ
Debit: -0.50000000 BTC
Transaction fee: -0.00002260 BTC
Net amount: -0.50002260 BTC
Transaction ID: f062603df20f27e816d579f6e9f478dd4e081b51adf8385b4780d6e67dd8d9b8-000
Status: 0/unconfirmed
Date: 2/28/2016 18:25
To: MRR 14Ku5qudZD26kY4wPCDMHGcUk3UgaU4q1H
Debit: -0.50000000 BTC
Transaction fee: -0.00003740 BTC
Net amount: -0.50003740 BTC
Transaction ID: 910904897349eb6de01ccc037ad7404aebe5c9edb3d5d08118da0fa4e9e0208c-000
Topic: My Bitcoins Are Stuck - Unconfirmed After 20 Hours - page 2. (Read 3339 times)
I always send double the minimum fee because I like fast confirms.
I guess there is nothing you can do and most likely it will get confirmed eventually... but at least you will save about 100 bits for the delay. Which wallet/client were you using?
It's been like this for quite some time now, you can't rely on the network, you better stay off bitcoin or use other alternative payment system.
It will only get worst, well, unless people stop using bitcoin...
It will only get worst, well, unless people stop using bitcoin...
Now, I know the first thing you'll think is that I didn't set a fee. I did. I'd never be cheeky enough to do zero fees!
Status: 0/unconfirmed, broadcast through 11 nodes
Date: 28/02/2016 14:23
To: Escrow 1Nw3CeDgELL3DjorxHK5ehR5upQ2PN1rd
Debit: -0.25000000 BTC
Transaction fee: -0.00001130 BTC
Net amount: -0.25001130 BTC
Transaction ID: 0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224-000
The fee I set was based on the minimum recommended, which is what I always use. It's never taken this long before.
Is this because there's a problem with the network or is it because the miners want a larger fee?
I need to send the same amount again and while I could up the fee, I may end up not upping it enough or upping it too much.
Advice please from you lovelies?
Someone has switched on her spam-script again today. It was off for a while. It only cost about 3 BTC per hour to keep most normal transactions delayed, and someone keep doing that frequently. I have no idea why, but suspect it is related to current events where Coinbase and some helpers are trying to gain control over Bitcoin.Status: 0/unconfirmed, broadcast through 11 nodes
Date: 28/02/2016 14:23
To: Escrow 1Nw3CeDgELL3DjorxHK5ehR5upQ2PN1rd
Debit: -0.25000000 BTC
Transaction fee: -0.00001130 BTC
Net amount: -0.25001130 BTC
Transaction ID: 0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224-000
The fee I set was based on the minimum recommended, which is what I always use. It's never taken this long before.
Is this because there's a problem with the network or is it because the miners want a larger fee?
I need to send the same amount again and while I could up the fee, I may end up not upping it enough or upping it too much.
Advice please from you lovelies?
Some pools filter the spam quite efficiently. If e.g. Eligius manage to mine a block, your transaction will probably be in it.
I just coped and pasted the transaction details from my bitcoin client. the -000 was part of it.Strange! For a minute I wondered if I'd sent to the wrong bitcoin address! 
So, if the recommended minimum is too low, what should I input manually? I am really bad with decimals and afraid of putting it in the wrong place and emptying my wallet by mistake!
Thanks for your response.
So, if the recommended minimum is too low, what should I input manually? I am really bad with decimals and afraid of putting it in the wrong place and emptying my wallet by mistake!
Thanks for your response.
Not sure why you have posted the wrong transaction address but I did check the sent address and this is the correct transaction address instead: https://blockchain.info/tx/0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224 (No -000 in the end)
Your fee is still below the required amount of 0.0001 as standard fee for each transaction (at least) and you only sent 0.0000113 as a fee. For some reason on the "Estimated Confirmation Time has stated: Very Soon (High Priority)" even though it shouldn't be like that. My guess would be, it will either get confirmed in the next day or it will just get cancelled and go back to your wallet again.
Your fee is still below the required amount of 0.0001 as standard fee for each transaction (at least) and you only sent 0.0000113 as a fee. For some reason on the "Estimated Confirmation Time has stated: Very Soon (High Priority)" even though it shouldn't be like that. My guess would be, it will either get confirmed in the next day or it will just get cancelled and go back to your wallet again.
Not sure why you have posted the wrong transaction address but I did check the sent address and this is the correct transaction address instead: https://blockchain.info/tx/0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224 (No -000 in the end)
Your fee is still below the required amount of 0.0001 as standard fee for each transaction (at least) and you only sent 0.0000113 as a fee. For some reason on the "Estimated Confirmation Time has stated: Very Soon (High Priority)" even though it shouldn't be like that. My guess would be, it will either get confirmed in the next day or it will just get cancelled and go back to your wallet again.
Your fee is still below the required amount of 0.0001 as standard fee for each transaction (at least) and you only sent 0.0000113 as a fee. For some reason on the "Estimated Confirmation Time has stated: Very Soon (High Priority)" even though it shouldn't be like that. My guess would be, it will either get confirmed in the next day or it will just get cancelled and go back to your wallet again.
Now, I know the first thing you'll think is that I didn't set a fee. I did. I'd never be cheeky enough to do zero fees!
Status: 0/unconfirmed, broadcast through 11 nodes
Date: 28/02/2016 14:23
To: Escrow 1Nw3CeDgELL3DjorxHK5ehR5upQ2PN1rd
Debit: -0.25000000 BTC
Transaction fee: -0.00001130 BTC
Net amount: -0.25001130 BTC
Transaction ID: 0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224-000
The fee I set was based on the minimum recommended, which is what I always use. It's never taken this long before.
Is this because there's a problem with the network or is it because the miners want a larger fee?
I need to send the same amount again and while I could up the fee, I may end up not upping it enough or upping it too much.
Advice please from you lovelies?
Intermediary
Status: 0/unconfirmed, broadcast through 11 nodes
Date: 28/02/2016 14:23
To: Escrow 1Nw3CeDgELL3DjorxHK5ehR5upQ2PN1rd
Debit: -0.25000000 BTC
Transaction fee: -0.00001130 BTC
Net amount: -0.25001130 BTC
Transaction ID: 0f63833cb3ce6a324e65985b1e84368ea633114d478599c511983b57f2f0c224-000
The fee I set was based on the minimum recommended, which is what I always use. It's never taken this long before.
Is this because there's a problem with the network or is it because the miners want a larger fee?
I need to send the same amount again and while I could up the fee, I may end up not upping it enough or upping it too much.
Advice please from you lovelies?
Intermediary
Jump to: