Bitcoin Forum
June 14, 2024, 11:33:20 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: My bitcoin-qt wont discover a unconfirmed transaction.  (Read 1951 times)
Mysticsam_3579 (OP)
Newbie
*
Offline Offline

Activity: 30
Merit: 0


View Profile
December 05, 2013, 09:43:43 PM
 #1

Hi everyone

My bitcoin-qt 0.8.5-beta on a Debian 7 wont discover a unconfirmed transaction. It wont get the transaction until it have got in to a block. I don't like that i wont see a incoming transaction until it have become confirmed.

Please tell me if you guys and girls need more info about this to help me out.
mikenekro
Newbie
*
Offline Offline

Activity: 57
Merit: 0


View Profile
December 06, 2013, 12:47:59 AM
 #2

I am having the same problem. The bitcoin was sent over an hour ago. It shows as unconfirmed on blockchain but fails to appear in my wallet.

https://blockchain.info/address/1LQ9mnhGeKsuK3MXjvjpvSmAKgJxKwdZMT

Any help would be great! For both of us
Mysticsam_3579 (OP)
Newbie
*
Offline Offline

Activity: 30
Merit: 0


View Profile
December 07, 2013, 11:55:33 AM
 #3

No one else that is having this issue? or someone that can help us?
DannyHamilton
Legendary
*
Offline Offline

Activity: 3416
Merit: 4658



View Profile
December 10, 2013, 06:20:21 PM
 #4

Was your Bitcoin-Qt running when the transaction was broadcast?  Was it connected to peers? Was synchronization caught up?

If not, then your Bitcoin-Qt missed the initial relay of the transaction and therefore has not heard about it.

It will discover the transaction when it receives it in a block.

If your Bitcoin-Qt was running, was synchronized, and was connected to peers when the transaction was boadcast, then it should have heard about the transaction and displayed it as "unconfirmed".
mikenekro
Newbie
*
Offline Offline

Activity: 57
Merit: 0


View Profile
December 10, 2013, 09:15:28 PM
 #5

Was your Bitcoin-Qt running when the transaction was broadcast?  Was it connected to peers? Was synchronization caught up?

If not, then your Bitcoin-Qt missed the initial relay of the transaction and therefore has not heard about it.

It will discover the transaction when it receives it in a block.

If your Bitcoin-Qt was running, was synchronized, and was connected to peers when the transaction was boadcast, then it should have heard about the transaction and displayed it as "unconfirmed".



I figured out the problem. It was synchronized connected and open. It was not shown as unconfirmed. Nothing was in the wallet. This was because it was sent without a fee. It had to wait in line and therefore did not show up, even as unconfirmed, in my wallet. It showed up on blockchain though. Had to wait about 5 or 6 hours to go through and show up.

If anyone else has this problem check blockchain to see if it sent with a fee.
Mysticsam_3579 (OP)
Newbie
*
Offline Offline

Activity: 30
Merit: 0


View Profile
December 14, 2013, 10:01:04 PM
 #6

I think that my client was syncing when i did the transaction. So thanks for giving me a answer to my problem, but i feel that the client should be able  to listen to new transactions and syncing up to the blockchain at the same time dont you?
DannyHamilton
Legendary
*
Offline Offline

Activity: 3416
Merit: 4658



View Profile
December 15, 2013, 07:17:18 AM
 #7

I think that my client was syncing when i did the transaction. So thanks for giving me a answer to my problem, but i feel that the client should be able  to listen to new transactions and syncing up to the blockchain at the same time dont you?

It has to have the blockchain to verify that the transaction is valid.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!