Topic: Transaction not confirmed (Read 1567 times)
All my transactions are back on Blockchain and confirmed by this morning.
I think that's normal with the stress blockchain is suffering last days
i think its not since the stress test is done (i think) coz there are no spam on the network on the last 7days atleast
i think the only problem is on different block explorer
I think that's normal with the stress blockchain is suffering last days
I sent two separate transactions of similar amounts today. One from my breadwallet app (default fee?), and one from my electrum wallet (0.0003 BTC). I sent the breadwallet late this morning. It still hasn't confirmed. The electrum confirmed in no time.
I read that the breadwallet default fee is too low at the moment, so that's why it's taking forever. Makes cents to me. (See what I did there?)
Regards,
Christopher
I read that the breadwallet default fee is too low at the moment, so that's why it's taking forever. Makes cents to me. (See what I did there?)
Regards,
Christopher
I sent 3 transactions, all disappeared from blockchain with the message:
They still show up on Blockr.io
This is annoying. Good thing I don't absolutely require these funds in the next 48 hours...
Check from btc.blockr.io Quote
Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database.
They still show up on Blockr.io
This is annoying. Good thing I don't absolutely require these funds in the next 48 hours...
blockchain.info is screwed up right now.
I sent 3 transactions, all disappeared from blockchain with the message:
They still show up on Blockr.io
This is annoying. Good thing I don't absolutely require these funds in the next 48 hours...
Quote
Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database.
They still show up on Blockr.io
This is annoying. Good thing I don't absolutely require these funds in the next 48 hours...
Jorge Stolfi said another stress test had started but there are only a few thousand unconfirmed transactions tonight. It might be the reason for the delay the OP has. I ignored it until now and hoped the test would stop before it did any damage. I hope it doesn't last for days like the last time when there were 10 thousand unconfirmed transactions.
How accurate are these figures? Its a simulation of a model of the system, so doubly removed!!.
As the dev admits, " the main tradeoff, however, is the dependence on the model assumptions"
AFAIK, the "simulation" is only for the top graph (what fees you would need to get expectation of N minutes to first confirmation), and for the dashed line (capacity) on the bottom graph. The backlog (solid line) and incoming traffic (dotted) on the bottom graph are real data.
The information about the fees being paid by teh unconfirmed transactions comes from this other site. The big step at 0.20 mBTC/kB must be largely due to the test transactions.
Right now there appeared another large step at ~0.50 mBTC/kB; that may be test transactions, too. However, those transctions are still below the 750 kB level, so they may affect only those transactions (a few thousand?) that paid between 0.20 and 0.35 (beware that the graph is changing all the time). But they may be a sign that the "tester" is raising his annoyance goal...
-snip-
Another "stress test" just started. The backlog is already 60 MB of unconfirmed transactions, and the input traffic is ~ 3 MB every 10 minutes, or ~5 kB/s . So far, the tester is paying 0.2 mBTC/kB, like the last one. Will it keep at that, or increase the fees later?
How accurate are these figures? Its a simulation of a model of the system, so doubly removed!!.
As the dev admits, " the main tradeoff, however, is the dependence on the model assumptions"
AFAIK, the "simulation" is only for the top graph (what fees you would need to get expectation of N minutes to first confirmation), and for the dashed line (capacity) on the bottom graph. The backlog (solid line) and incoming traffic (dotted) on the bottom graph are real data.
The information about the fees being paid by teh unconfirmed transactions comes from this other site. The big step at 0.20 mBTC/kB must be largely due to the test transactions.
Right now there appeared another large step at ~0.50 mBTC/kB; that may be test transactions, too. However, those transctions are still below the 750 kB level, so they may affect only those transactions (a few thousand?) that paid between 0.20 and 0.35 (beware that the graph is changing all the time). But they may be a sign that the "tester" is raising his annoyance goal...
-snip-
Not that they are starting to get greed, it's just that there are other transactions in the queue that paid higher fees for their transactions to get through first. 
That would sound reasonable if every block was filled up to its limit of 1MB, but that's not the case. Some miners (or rather, mining pool operators) don't make sense.
However, a 0.0001 fee should be absolutely fine. I think it's just bad luck that the tx didn't get confirmed yet (and that backlog isn't helping either), but it most certainly will be confirmed eventually.
i have got some trouble too i previously sent 0.015 with 0.0001 fee and it is still not confirmed after that i made 0.02 tx and it has 2 confirmations now
Congestion WEATHER : http://statoshi.info/dashboard/db/transactions
Actual fee : http://bitcoinexchangerate.org/fees
0,2 mBTC.
Actual fee : http://bitcoinexchangerate.org/fees
0,2 mBTC.
Then perhaps my fees of 0.0001 are not high enough. Miners are starting to get greedy 
Not that they are starting to get greed, it's just that there are other transactions in the queue that paid higher fees for their transactions to get through first.
To add to dothebeats comment, it would not NEVER be profitable to sit back and not confirm. Miners will always chose to include your transaction if there are no other with higher priority.
I think your fee is fine, but I strongly suggest avoiding online wallets and relying on something else than a node for transactions.
Considering all the noise on blockchain.info, you might want to use another blockchain explorer.
There're 6 MB of backlogged tx'es right now.
https://blockchain.info/unconfirmed-transactions
You might wait a few longer.
https://blockchain.info/unconfirmed-transactions
You might wait a few longer.
yeah lately blockchain often unconfirmed,
perhaps because many use, regardless of fee as it has no effect if the troubled bitcointalk
perhaps because many use, regardless of fee as it has no effect if the troubled bitcointalk
Then perhaps my fees of 0.0001 are not high enough. Miners are starting to get greedy
Not that they are starting to get greed, it's just that there are other transactions in the queue that paid higher fees for their transactions to get through first.
Then perhaps my fees of 0.0001 are not high enough. Miners are starting to get greedy
I have 3 separate transactions that are still unconfirmed after 3 hours... 
It'll confirm eventually but DANG this is annoying. Need to upgrade QT I guess.
It'll confirm eventually but DANG this is annoying. Need to upgrade QT I guess.
I don't know what would be the difference in confirmation times if you change your client. The transaction confirmation time depends on the miners' side, not on the client that you are using.
so i sent a normal bitcoin transaction of 0.01 bitcoin with 0.0001 fee like an hour ago from blockchain wallet and it does not get confirmed, is it because of that blockchain bug?
Nah, the blockchain bug (the one with the spent Satoshi balance, if that's what you're talking about) isn't the one that caused the delays on the confirmation of your transaction. Honestly, 0.0001 is a fairly nice fee you can put if you want your transactions to be confirmed. Most of the transactions I see now only put 0.0001 as a transaction fee.
I have 3 separate transactions that are still unconfirmed after 3 hours...
It'll confirm eventually but DANG this is annoying. Need to upgrade QT I guess.
It'll confirm eventually but DANG this is annoying. Need to upgrade QT I guess.
0.0001 as a fee is decent (assuming your transaction isn't ridiculous on outputs/inputs).
It's incredibly unlikely that a bug occurs in the Blockchain, the problem will almost always be you.
To me, it seems like you've just been unlucky. Luck does play a role in how the transaction gets picked up for confirmation.
It's incredibly unlikely that a bug occurs in the Blockchain, the problem will almost always be you.
To me, it seems like you've just been unlucky. Luck does play a role in how the transaction gets picked up for confirmation.
so i sent a normal bitcoin transaction of 0.01 bitcoin with 0.0001 fee like an hour ago from blockchain wallet and it does not get confirmed, is it because of that blockchain bug?
No, seems that your fee was too low.
In the future, before you send your transaction,
you should check the status of the mempool,
then apply your miner fee accordingly.
This is where I check the status: https://tradeblock.com/blockchain/
This is a site which advises a fee based on mempool: https://bitcoinfees.github.io/
According to above, you should have paid around 0.0003 BTC for next block, in theory.
Jump to: