Bitcoin Forum
June 07, 2024, 09:22:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Conflicted transaction  (Read 830 times)
Matijash89 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 16, 2016, 07:48:49 PM
 #1

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.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3416
Merit: 6678


Just writing some code


View Profile WWW
January 16, 2016, 07:49:39 PM
 #2

What is the transaction id of that transaction?

Matijash89 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 16, 2016, 07:59:59 PM
 #3

That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05
Your Point Is Invalid
Hero Member
*****
Offline Offline

Activity: 756
Merit: 510


Dear me, I think I'm becoming a god


View Profile WWW
January 16, 2016, 08:01:27 PM
 #4

it seems the transaction was rejected by the network, try sending the coins again with fee

achow101
Moderator
Legendary
*
Offline Offline

Activity: 3416
Merit: 6678


Just writing some code


View Profile WWW
January 16, 2016, 08:05:06 PM
 #5

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.

Matijash89 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 16, 2016, 08:11:11 PM
 #6

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.
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
January 16, 2016, 08:11:26 PM
 #7

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?

Im not really here, its just your imagination.
Matijash89 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 16, 2016, 08:18:03 PM
 #8

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  Sad
After the transaction was created I performed an update to the wallet and now it's  0.11.2
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
January 16, 2016, 08:19:14 PM
 #9

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  Sad
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.

Im not really here, its just your imagination.
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!