Author

Topic: Transaction stuck for an hour in "unconfirmed" status (Read 1244 times)

legendary
Activity: 2898
Merit: 1253
So anyway, I applied as a merit source :)
This can happen in case your bitcoin core software is still newly installed on your machine and it requires some time to sync with the network and grab the 7 years of blockchain.

However I suggest you to be patient as sometimes the network is lagging and slow, Since you have paid mining fee it should get confirmed if not in 4 hours.
legendary
Activity: 3276
Merit: 1029
Leading Crypto Sports Betting & Casino Platform
As knightdk mentioned, the Bitcoin Core client tells you that it may take up to 25 blocks to confirm if you leave the default setting.



You might get lucky and have it confirmed in the next block, but if it ends up taking the entire 25 blocks at an average of 10 minutes per block you should expect it to take up to 4.5 hours to confirm.

If you just started up your client and it hasn't had time to get a good sense of current confirmation times before you send your transaction, then it could estimate incorrectly and take even longer than that.
Well, this problem is happened for me yesterday but thank this answer really helpful for me, i just waiting until several hours for the unconfirmed transaction for getting confirm.
full member
Activity: 224
Merit: 100
As knightdk mentioned, the Bitcoin Core client tells you that it may take up to 25 blocks to confirm if you leave the default setting.



You might get lucky and have it confirmed in the next block, but if it ends up taking the entire 25 blocks at an average of 10 minutes per block you should expect it to take up to 4.5 hours to confirm.

If you just started up your client and it hasn't had time to get a good sense of current confirmation times before you send your transaction, then it could estimate incorrectly and take even longer than that.

Yeah, when you send transaction using the default fee. The priority was not that high and there is less rate that it will be confirmed fast. Butnif you are lucky. Confirmation can occur in just an hour after the trnsaction was created. But sometimes it is slow because of the traffic and there are many high priority transaction occur making your transaction stacked on the bottom.
legendary
Activity: 3472
Merit: 4801
As knightdk mentioned, the Bitcoin Core client tells you that it may take up to 25 blocks to confirm if you leave the default setting.



You might get lucky and have it confirmed in the next block, but if it ends up taking the entire 25 blocks at an average of 10 minutes per block you should expect it to take up to 4.5 hours to confirm.

If you just started up your client and it hasn't had time to get a good sense of current confirmation times before you send your transaction, then it could estimate incorrectly and take even longer than that.
staff
Activity: 3458
Merit: 6793
Just writing some code
I sent a transaction an hour ago through Bitcoin Core using the default fee, and it's still unconfirmed. Is something going on with the network? I have never had problems with Bitcoin Core when sending a transaction using the recommended fee, but this time its taking too long. It's already past 1 hour actually.
Well the default recommended fee is for it to confirm within 25 blocks, so don't be too surprised that it is slow. If you want fast confirmations, you have to move the slider all the way to the right to "fast".
legendary
Activity: 4228
Merit: 1313
I sent a transaction an hour ago through Bitcoin Core using the default fee, and it's still unconfirmed. Is something going on with the network? I have never had problems with Bitcoin Core when sending a transaction using the recommended fee, but this time its taking too long. It's already past 1 hour actually.

Do you have the transaction id?
legendary
Activity: 1610
Merit: 1183
I sent a transaction an hour ago through Bitcoin Core using the default fee, and it's still unconfirmed. Is something going on with the network? I have never had problems with Bitcoin Core when sending a transaction using the recommended fee, but this time its taking too long. It's already past 1 hour actually.
Jump to: