Bitcoins not showing up on the blockchain?

[Sakarias-Corporation]

Hello yeasterday my friend was going to send me .4 BTC. He got a Hash but it won't work or show up on blockchain.info.
It's been 13 hours now and the coins are still not showing up.


I used team viewer to check his wallet.

I can confirm that he did send the coins and got a hash.

It's 100% to the right adress.

Now thing is his wallet was 180 weeks behind something when he sent (it was still syncing)

We both had to sleep at that point and go to work today so neither of us can check his wallet now for some hours to see what happened, but anyway can the syncing of his wallet cause this problem?
Will the coins be sent once it's fully sync ? Or are we fucked ?

[Amph]

can you provide the address to which the coins were sent? i think he sent them without fees

[icey]

His wallet will need to be fully synced

[DarkHyudrA]

His wallet will need to be fully synced

This. As soon as it gets synced it will send the transaction.
The reason for that is pretty obvious: your address with the 0.4BTC could be already be used sometime in those 13180 weeks late of blocks, and then Bitcoin Core would fail and allow double spends.

can you provide the address to which the coins were sent? i think he sent them without fees

The Bitcoin-qt doesn't allow this. (unless you get the non official fork that allows that)

[countryfree]

Now thing is his wallet was 180 weeks behind something when he sent (it was still syncing)

Wait!
As a rule, you should not do anything with a wallet which isn't synced. I guess your friend had old software, too.

[cakir]

It's not broadcasted yet.

But you can broadcast it manually then it'll be accepted and show up on the network.
first your friend needs to extract the raw transaction from the core wallet. (he/she can do it from console)
then it's needed to be broadcasted on here: http://blockchain.info/pushtx or here: https://btc.blockr.io/tx/push#!

[cryptworld]

It's not likely but hope your friend hadn't a very old wallet,cause it could be forked, but don't worry,you have not lost it any way

[Amph]

His wallet will need to be fully synced

This. As soon as it gets synced it will send the transaction.
The reason for that is pretty obvious: your address with the 0.4BTC could be already be used sometime in those 13180 weeks late of blocks, and then Bitcoin Core would fail and allow double spends.

can you provide the address to which the coins were sent? i think he sent them without fees

The Bitcoin-qt doesn't allow this. (unless you get the non official fork that allows that)

ah yeah you are right, is this feature coming for the next qt version? would be helpful for certain situation

[Sakarias-Corporation]

He had the latest version but had to re-update the wallet.

I'm not home yet not is he so we don't know if it's uppdated yet, tho it's been 20 hours something now.

But I'll send a update as soon as I'm home

[Sakarias-Corporation]

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


This is the adress for those who would like to know

[Sakarias-Corporation]

Some news. The wallet is uppdated. Coins are gone but no transaction took place. He said something about that the wallet said it was "conflicted" It was in swedeish so I'm just "hard" translating

[cakir]

Some news. The wallet is uppdated. Coins are gone but no transaction took place. He said something about that the wallet said it was "conflicted" It was in swedeish so I'm just "hard" translating

Probably chain is not synced properly.
Before deleting all chain your friend should try those commands on bitcoin console;
salvagewallet
repairwallet

One of those will try to correct the wallet. if it doesn't work then it's needed to resync the block chain.

[DarkHyudrA]

Some news. The wallet is uppdated. Coins are gone but no transaction took place. He said something about that the wallet said it was "conflicted" It was in swedeish so I'm just "hard" translating

Probably is the problem of only 8 connections, nothing to worry I would say.
But since the transaction is recent, just sit down some minutes and watch: your transaction probably got relayed now and a miner soon will put it on a block and it will get it's first confirmation.

[Sakarias-Corporation]

Some news. The wallet is uppdated. Coins are gone but no transaction took place. He said something about that the wallet said it was "conflicted" It was in swedeish so I'm just "hard" translating

Probably is the problem of only 8 connections, nothing to worry I would say.
But since the transaction is recent, just sit down some minutes and watch: your transaction probably got relayed now and a miner soon will put it on a block and it will get it's first confirmation.

But if so, I should see it with 0 confirmations right ?

[DannyHamilton]

Since they sent the transaction before their wallet was fully synchronized, their wallet wouldn't have known about all the unsynchronized transactions.  Therefore, in the transaction being sent to you, it probably spent outputs that it thought were unspent, but that were actually already spent in the part of the blockchain that it hadn't yet processed. Then later, when it finally processed those other transactions, it likely became "conflicted" since it discovered that it tried to spend the same outputs twice.

If your friend runs their wallet with the -zapwallettxes command line option, it will "forget" all the transactions that it has built, and then it will re-scan the entire blockchain to rebuild the valid list of confirmed transactions that have been sent to and from that wallet.  When the re-scan is complete, they should see the coins are no longer "gone" (or if they are gone, then they should have the transaction history to see where the coins actually went).

If your friend is uncomfortable with running zapwallettxes, can you perhaps get your friend to supply us with the output after running the following command in the console:

Code:

getrawtransaction txid

Where txid is the transaction hash that their wallet says they sent to you?

That information should be enough to determine what outputs the wallet attempted to spend and why it was unable to do so.

[Sakarias-Corporation]

Since they sent the transaction before their wallet was fully synchronized, their wallet wouldn't have known about all the unsynchronized transactions.  Therefore, in the transaction being sent to you, it probably spent outputs that it thought were unspent, but that were actually already spent in the part of the blockchain that it hadn't yet processed. Then later, when it finally processed those other transactions, it likely became "conflicted" since it discovered that it tried to spend the same outputs twice.

If your friend runs their wallet with the -zapwallettxes command line option, it will "forget" all the transactions that it has built, and then it will re-scan the entire blockchain to rebuild the valid list of confirmed transactions that have been sent to and from that wallet.  When the re-scan is complete, they should see the coins are no longer "gone" (or if they are gone, then they should have the transaction history to see where the coins actually went).

If your friend is uncomfortable with running zapwallettxes, can you perhaps get your friend to supply us with the output after running the following command in the console:

Code:

getrawtransaction txid

Where txid is the transaction hash that their wallet says they sent to you?

That information should be enough to determine what outputs the wallet attempted to spend and why it was unable to do so.

Hey, thanks I will inform him of this, this is the txid he got
fa44f90816a02c4d4f96eb2361f4749a7c83311f8989a68c5172cc6903d64ae3-000

[DannyHamilton]

- snip -
this is the txid he got
fa44f90816a02c4d4f96eb2361f4749a7c83311f8989a68c5172cc6903d64ae3-000

Can he run:

Code:

getrawtransaction fa44f90816a02c4d4f96eb2361f4749a7c83311f8989a68c5172cc6903d64ae3

In the console of the "Debug Window" in the "Help" menu, and let us know what the output of that command was?

[Sakarias-Corporation]

- snip -
this is the txid he got
fa44f90816a02c4d4f96eb2361f4749a7c83311f8989a68c5172cc6903d64ae3-000

Can he run:

Code:

getrawtransaction fa44f90816a02c4d4f96eb2361f4749a7c83311f8989a68c5172cc6903d64ae3

In the console of the "Debug Window" in the "Help" menu, and let us know what the output of that command was?

He tried. Client crashed and he had to make a restart... Hehe

[Sakarias-Corporation]

Getting worried now... Something like this actually happened before to, for a year ago. 2 BTC never got broadcasted or something

[crazyivan]

Yes, try checkwallet and then repairwallet commands.

This might fix the issue.