-
|
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hello, your transaction spends a coinjoin output that is still unconfirmed. You need this coinjoin (the parent transaction) to be confirmed for your new transaction (the child) to be confirmed afterwards. You are performing what is called a CPFP, which means that the high fee being paid by your transaction helps a bit to make the coinjoin confirm faster. The problem is that a coinjoin is really big, therefore this has very little impact on when it will be confirmed, Unfortunately, you have no other solution than wait or cancel the transaction (right-click cancel). The fee paid by coinjoins is optimized to be high enough so the confirmation is fast, but not too high so not too much money is wasted in fees. Estimating the confirmation time is an impossible science, because some unforeseeable events might happen, which makes the mempool to grow, and the coinjoins to sit there unconfirmed for quite some time. For privacy reasons, I suggest you to delete your txid |
Beta Was this translation helpful? Give feedback.
-
|
Another "costly" option is to speed up the transaction by bumping its fee (RBF) which what OP has done and both the coinjoin tx and the replacing tx got confirmed. |
Beta Was this translation helpful? Give feedback.
Hello, your transaction spends a coinjoin output that is still unconfirmed. You need this coinjoin (the parent transaction) to be confirmed for your new transaction (the child) to be confirmed afterwards. You are performing what is called a CPFP, which means that the high fee being paid by your transaction helps a bit to make the coinjoin confirm faster. The problem is that a coinjoin is really big, therefore this has very little impact on when it will be confirmed,
Unfortunately, you have no other solution than wait or cancel the transaction (right-click cancel). The fee paid by coinjoins is optimized to be high enough so the confirmation is fast, but not too high so not too much money i…