Unconfirmed Transaction

[nschmid]

I have read about similar issues on the forums and could not find an applicable solution.

I originally sent an amount of BTC but realized after that the fee was quite low.  I cleared all unconfirmed transactions and rebuilt and rescanned the databases.  Sending a new transaction with a higher fee resulted in an error so I updated Bitcoin Core to 14.1 and Armory to 0.96.

Sending a transaction with a large fee (intended to help confirm quickly) failed due to error 'dust', so I used the recommended fee amount for the transaction.  The transaction seemed to be successful but is now stuck at 0 confirmations after ~24 hrs. 

I am not sure what else to try, any ideas?

Links to first and second transaction for reference:

https://blockchain.info/address/1GMkvJP2P14nm42uT2CsRLz16ZyfeBeqpF
https://blockchain.info/address/1Pdor1eHGn5EXasib2hC8GWSqpKo4Coqsj

Thanks,
Nathan

[1715586759]

1715586759

[1715586759]

1715586759

[1715586759]

1715586759

[gangtraet]

Both transactions have low fees, but the second should confirm after a while.  However, it is a double spend of the first transaction, so it may not propagate well on the network since nodes that have already seen the first transaction will not propagate the second.

Unfortunately, there is probably not much you can do, except waiting until either one of the transactions confirm, or until they time out so you can resend.  The Bitcoin network is in very bad shape right now; and the community is divided, in even worse shape, and unable to do anything about the capacity problems Bitcoin is facing. 

[goatpig]

CPFP

[nschmid]

Thank you for the replies,

It seems the initial transaction did in fact time out and is no longer on the network.  Does this mean the second transaction is no longer dependent on the first transaction as a double spend?

[Mr.Vice]

Both transactions have low fees, but the second should confirm after a while.  However, it is a double spend of the first transaction, so it may not propagate well on the network since nodes that have already seen the first transaction will not propagate the second.

Unfortunately, there is probably not much you can do, except waiting until either one of the transactions confirm, or until they time out so you can resend.  The Bitcoin network is in very bad shape right now; and the community is divided, in even worse shape, and unable to do anything about the capacity problems Bitcoin is facing. 

hmmm... when does a transaction usually time out in the mempool?

[goatpig]

72h I believe.

[nschmid]

Just an update to anyone who comes across this.

It took approximately 8 days for the first transaction to time out.  Once the first transaction timed out the second transaction was confirmed within hours.