Title: Weird transaction fee issue transaction not confirming Post by: bucketofsocks on November 21, 2013, 01:31:19 AM Posted in another thread and it was suggested I start a new topic here
I'm running Bitcoin-qt 0.8.4 on windows and I tried to send some bitcoin over 24 hours ago, it came up with a message about paying a fee of 0.0005 and I clicked yes but for some reason it only included 0.00006438 as the fee and now the transaction is stuck in limbo https://blockchain.info/tx/f1903e97d2c96e3bfb975dfa23a2c8de72c68df1e843db8c842a6c87bfdb32c9 is there anything I can do? getinfo 19:23:25  { "version" : 80400, "protocolversion" : 70001, "walletversion" : 60000, "balance" : 0.03082213, "blocks" : 270694, "timeoffset" : 1, "connections" : 81, "proxy" : "", "difficulty" : 609482679.88835454, "testnet" : false, "keypoololdest" : 1372280961, "keypoolsize" : 101, "paytxfee" : 0.00010000, "errors" : "" } Title: Re: Weird transaction fee issue transaction not confirming Post by: bucketofsocks on November 21, 2013, 03:59:58 AM The transaction has disappeared off of blockchain.info so I followed the instructions for purging it from my wallet and ran bitcoin -rescan
The transaction no longer shows in my wallet but I didn't get my coins back, is there anything I can do? Title: Re: Weird transaction fee issue transaction not confirming Post by: BurtW on November 21, 2013, 08:40:22 AM If this is the transaction you are looking at/for:
https://blockchain.info/tx/f1903e97d2c96e3bfb975dfa23a2c8de72c68df1e843db8c842a6c87bfdb32c9 It has been sent and spent already. It was spent in this transaction: https://blockchain.info/tx/89743cf8215290113665cf71e581a78228afa48c5b3f667320a351afc972b400 Your 0.63590622 BTC are now here: https://blockchain.info/address/1MAi5MVfsBfPUisN1fgk3JXLL3KFeUVxiB Title: Re: Weird transaction fee issue transaction not confirming Post by: bucketofsocks on November 21, 2013, 10:55:58 PM yeah it disappeared from blockchain.info last night and I panicked went through all the pywallet stuff to try to get my coins back then this morning it showed back up as confirmed, I just jumped the gun and overreacted. 52 hours does seem excessive for the confirm time though
|