|
Title: Conflicted transaction Post by: Matijash89 on January 16, 2016, 07:48:49 PM Hi all,
I made a mistake and sent 0.4 btc without a fee from my wallet (old wallet version). That transaction is not confirmed on the blockchain and it shows Unspent. After that I installed the latest wallet version which is now showing Conflicted status for the transaction. My available balance is fine and it includes those 0.4 btc. Can you please let me know if 0.4 btc is really available or if they are lost on the network. I read an article about zapwallet but not sure about this command. Any help is greatly appreciated. Thanks. Title: Re: Conflicted transaction Post by: achow101 on January 16, 2016, 07:49:39 PM What is the transaction id of that transaction?
Title: Re: Conflicted transaction Post by: Matijash89 on January 16, 2016, 07:59:59 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05
Title: Re: Conflicted transaction Post by: Your Point Is Invalid on January 16, 2016, 08:01:27 PM it seems the transaction was rejected by the network, try sending the coins again with fee
Title: Re: Conflicted transaction Post by: achow101 on January 16, 2016, 08:05:06 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05 Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.Title: Re: Conflicted transaction Post by: Matijash89 on January 16, 2016, 08:11:11 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05 Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.Thanks, I will give it a try and see what happens. Title: Re: Conflicted transaction Post by: shorena on January 16, 2016, 08:11:26 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05 Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.bc.i says "High S", might be an old core version or a different client entirely. @Matijash89 which wallet software/service did you use to create the TX? Title: Re: Conflicted transaction Post by: Matijash89 on January 16, 2016, 08:18:03 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05 Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.bc.i says "High S", might be an old core version or a different client entirely. @Matijash89 which wallet software/service did you use to create the TX? I did create the transaction with an old core version, think it was 0.8.0.0 Haven't updated the wallet for a while :( After the transaction was created I performed an update to the wallet and now it's 0.11.2 Title: Re: Conflicted transaction Post by: shorena on January 16, 2016, 08:19:14 PM That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05 Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.bc.i says "High S", might be an old core version or a different client entirely. @Matijash89 which wallet software/service did you use to create the TX? I did create the transaction with an old core version, think it was 0.8.0.0 Haven't updated the wallet for a while :( After the transaction was created I performed an update to the wallet and now it's 0.11.2 Well than you can just zapwallettxes, let it do its thing and redo the TX. |