I am using the bitcoin qt 0.10.1 Wallet.
But the problem you are describing could be appropriate. I might had connected to a VPN during the bitcoin client was working.
Anyway this is a bug and should be fixed, shouldn´t it?
Topic: BitcoinQT: My transaction took over 30 minutes to propagate into the network (Read 862 times)
May 29, 2015, 10:18:11 AM
May 29, 2015, 10:14:38 AM
@medUSA yes, thank you for the correct phrase. I changed my topic subject accordingly.
About your questions. blockchain.info was not out of sync. I checked also on https://btc.blockr.io/ and at least the coinbase gateway didn´t receive the transaction details because it was not propagated in the timeframe of 10 minutes.
My internet connection is well and I had / have enough nodes.
Well the transaction was confirmed, but this is not the point. The problem is that my transaction was not propagated into the network and so I didn´t got my product from coinbase. Hopefully they already refunded me, but this is just a pain in the ass.
About your questions. blockchain.info was not out of sync. I checked also on https://btc.blockr.io/ and at least the coinbase gateway didn´t receive the transaction details because it was not propagated in the timeframe of 10 minutes.
My internet connection is well and I had / have enough nodes.
Well the transaction was confirmed, but this is not the point. The problem is that my transaction was not propagated into the network and so I didn´t got my product from coinbase. Hopefully they already refunded me, but this is just a pain in the ass.
What wallet are you using? Are you running the most recent version of that wallet?
I recall having an issue in older versions of Bitcoin Core where it would occasionally not broadcast a transaction if I sent it before the wallet had caught up with synchronization. This meant that if the wallet had been shut down for a day or two, and then I started it up and immediately sent a transaction, the transaction might not be broadcast for anywhere from 15 minutes to a few hours. I'd get around this issue by running "getrawtransaction" in the console and then copying and pasting the output into blockchain.info's transaction broadcasting service:
https://blockchain.info/pushtx
I haven't experienced this problem yet in the most recent version of Bitcoin Core.
May 29, 2015, 09:41:50 AM
@medUSA yes, thank you for the correct phrase. I changed my topic subject accordingly.
About your questions. blockchain.info was not out of sync. I checked also on https://btc.blockr.io/ and at least the coinbase gateway didn´t receive the transaction details because it was not propagated in the timeframe of 10 minutes.
My internet connection is well and I had / have enough nodes.
Well the transaction was confirmed, but this is not the point. The problem is that my transaction was not propagated into the network and so I didn´t got my product from coinbase. Hopefully they already refunded me, but this is just a pain in the ass.
About your questions. blockchain.info was not out of sync. I checked also on https://btc.blockr.io/ and at least the coinbase gateway didn´t receive the transaction details because it was not propagated in the timeframe of 10 minutes.
My internet connection is well and I had / have enough nodes.
Well the transaction was confirmed, but this is not the point. The problem is that my transaction was not propagated into the network and so I didn´t got my product from coinbase. Hopefully they already refunded me, but this is just a pain in the ass.
May 29, 2015, 07:08:14 AM
The priority is determined by your coin age and transaction size. In this case, your priority was 17,503,540. The minimum required for high priority is 28,000,000. The main reason for this was because of the transaction fees. Even though the minimum fees required for relay is 0.00001/kb(By default in Bitcoin Core), the priority was simply not high enough. Another possible factor is the block varience which can cause slower confirmations (Not in this case).
Edit: Just saw the issue about proporgation. This might still have some relevance since the priority was below maximum.
Edit: Just saw the issue about proporgation. This might still have some relevance since the priority was below maximum.
May 29, 2015, 07:04:03 AM
You mean your transaction took 30minutes to propagate to the network? Transactions usually take seconds to appear on the bitcoin network. It might not be your transaction, it could be blockchain.info being out of sync. It does happen. Next time use a second blockexplorer to check the network.
It could also be your internet connection or you were connected to a group of slow nodes when you send your transaction. The important thing is it is confirmed in 51 minutes, quite fair for that fee.
It could also be your internet connection or you were connected to a group of slow nodes when you send your transaction. The important thing is it is confirmed in 51 minutes, quite fair for that fee.
May 29, 2015, 06:28:47 AM
Hi, I am not talking about the confirmation. Only the Transaction details from my Bitcoin QT 0.10.1 Client to the Blockchain.
I was just trying to buy something online via coinbase gateway with a normal 10 minute timeperiod,
but my Transaction was settled in the blockchain over 30 minutes later. Attached the screenshot:
The blockchain.info hour is 2 hours behind
I was just trying to buy something online via coinbase gateway with a normal 10 minute timeperiod,
but my Transaction was settled in the blockchain over 30 minutes later. Attached the screenshot:
The blockchain.info hour is 2 hours behind
Jump to: