0

This question already has an answer here:

I did a transaction from my bitcoin core wallet. The transaction 6263452f635713e60f83d45fe41b1c9ba3b5f5e3af664778bf18a05b15cfde06 has not confirmed, and it is now over 48 hours since I made the transaction. Although blockchain.info will show the transaction (as unconfirmed) if I enter the transaction ID directly, it no longer shows it on the "unconfirmed transactions" page, https://blockchain.info/unconfirmed-transactions.

What should I do now? I am a complete newbie - this is my first transaction, and this has been very frustrating.

Thanks.

marked as duplicate by morsecoder Jul 13 '15 at 0:51

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • bitcoin infrastracture is under attack for the last few days, maybe because of that – user27369 Jul 12 '15 at 16:55
-1

Your transaction should be confirming shrtly(within 1 day)You did not send the appropriate miner fee which is why the transaction is slower to confirm. Do not worry tho it will confirm at some point tody:)

  • Thank you; I hope you're right. What is the "appropriate" miner fee? Inside bitcoin core, I set it at "normal"; is that a misleading setting? – Bernie L Jul 12 '15 at 14:52
  • If it hasn't confirmed within the last two days, what reason is there to think it will confirm today? – Nick ODell Jul 12 '15 at 17:27
  • @NickODell If the tx is valid, its expected confirmation time is 10 minutes, regardless of how long it has been unconfirmed already. Given, network congestion make this issue more complex, but essentially it's the same kind of statistics as block mining times: the average time to mine a block is 10 minutes. However, even if no block has been found for over 3 hours already, at that point the expected time to find the next block is still 10 minutes. – RocketNuts May 15 '16 at 13:36
  • @RocketNuts ...unless there's some problem that will prevent the transaction from getting into a block forever. – Nick ODell May 15 '16 at 23:50
  • @NickODell I'd say "some problem that will prevent the transaction from getting into a block forever" and the tx being valid are mutually exclusive? Maybe I'm missing something, but I can't think of a scenario where a tx is technically valid (and thus is getting relayed normally, i.e. not directly rejected by normal nodes) yet unable to ever be included in a block? – RocketNuts May 16 '16 at 13:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.