Bitcoin Forum
September 24, 2024, 03:03:22 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core transaction not reaching mempools (missing parents) on: January 03, 2018, 02:39:32 PM
Hi guys,

I bumped in almost the same issue like the guy who  started the post. I am pretty new to this  thing so please bare with me. So I received a transaction in my wallet - bitcoin core 0.15.1 - and I wanted to send transaction. When I didn't get confirmation for 24 hours I did some research and delete my mempool and started the wallet with -walletbroadcast=0 and I was able to abandon the transaction. So far so good - I did another transaction with more fee and now I am facing the same problem. When I check the old transaction in pushtx it gives me: transaction already exist and for the new transaction it gives me: Validation Error: BitcoindException(super=com.neemre.btcdcli4j.core.BitcoindException: Error #-26: 18: txn-mempool-conflict, code=-26)

Can you guys please help?

This is the rawhash of the first transaction:
02000000015410f3cbc047e5dc15d1b6d8fd4d8dbc46dded8f783e44704ebf67d0747f2a7c28000 0006a47304402201a9d0dae0edf0dded0a56a83637d53c4082eac0273735b96a638541af8acde31 02204a968b87310292c64fdafb009ad03f3897dbe35b092ef644d6b9cd2d5e7b1c190121039f65f 1a127600227bed752a25b1813bbffcae4ba194db09af38328d8911566e3feffffff0230954e0000 0000001976a9143c62cd65aa1284ad98e3013828e50f337de1312d88ac9b070000000000001976a 9148f0487148b0313078b0329a74d0ea84d21ffb68d88ac07aa0700

with transaction details:
1/3/18 00:38 Abandoned. Sent to (XXXXXXXXXXX) 16WHuR9ECniBVAXqGCM4mJeEgfRU925mwr -0.05154520


and this is the rawhash of the second - supposedly the replacement of the first one:
02000000015410f3cbc047e5dc15d1b6d8fd4d8dbc46dded8f783e44704ebf67d0747f2a7c28000 0006a47304402200893287fd5d5d98dd4385a21349edc0d05463f6cc703bc4b9e5099df1551d579 022057dfac558433b2c6b2df152ac62ee5da61e9889d9ad42b760554e9035220fa480121039f65f 1a127600227bed752a25b1813bbffcae4ba194db09af38328d8911566e3feffffff01ea3d4d0000 0000001976a9143c62cd65aa1284ad98e3013828e50f337de1312d88ac5baa0700

and again transaction details:
1/3/18 15:52 Unconfirmed. Sent to (XXXXXXXXXXXXX) 16WHuR9ECniBVAXqGCM4mJeEgfRU925mwr -0.05156467

Can you tell me what I am doing wrong and how can I prevent this from happening again?

Thanks in advance.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!