Author

Topic: Transaction made while offline, now not broadcasted? (Read 1537 times)

member
Activity: 67
Merit: 10
I've had this problem in the past. Old versions of the satoshi client can occaisionally fail in the manner you describe (transaction not being broadcast).

What version are you running?
sr. member
Activity: 339
Merit: 250
dafq is goin on
@ finway: I wrote: rescan and checkblocks did not help.... any suggestions?

Wink

but it was rebroadcasted after a while, so nutting to see here anymor, move on Wink ur coins did not become more valuable Wink
legendary
Activity: 2058
Merit: 1452
try

bitcoind.exe --rescan


he tried that (see op)
hero member
Activity: 714
Merit: 500
try

bitcoind.exe --rescan

sr. member
Activity: 339
Merit: 250
dafq is goin on
I did check if the transaction is out, but it was not broadcasted. I cant resend it, as the client thinks the coins are gone. But I know that they are not destroyed. Just takes some time, I guess it would have been broadcasted by now, if i had not deleted (have a abckup) everything to redownload the blockchain. Will tell tomorrow if its gone or not Wink
hero member
Activity: 714
Merit: 500
you can check your address at bitcoincharts.com/bitcoin,
see if your transaction has been in the unconfirmed transactions.

if not, just send it again.
sr. member
Activity: 339
Merit: 250
dafq is goin on
kaykay, made a backup, cleaned directory, downloading blockchain, will then copy wallet.dat into that directory, if same trouble, i let it run. If after 1 day no broadcast, ill put in the backup and try for 1 day. and after that i gues i have to extract the private keys or sth similar....

thx so far
legendary
Activity: 2058
Merit: 1452
leave it running for a few hours, it will rebroadcast. (worked for me :p)
sr. member
Activity: 339
Merit: 250
dafq is goin on
Hiho, I made a transaction. After two hours I realized, that tor was not connected, so connected tor. Had one connection then 0 connections. change setting to "no proxy" in btc client. Restarted client. Now transaction sits there, is not broadcast, and does not get confirmed. rescan and checkblocks did not help.... any suggestions?
Jump to: