<p>That's correct, a transaction cannot be confirmed until all its inputs (and all of their inputs, and so on) have confirmed.  (It is allowed for the transaction to go in the same block as its inputs, so that they confirm simultaneously.)</p>

<p>You may be able to remedy the situation by creating a third transaction that spends the second (7da9), with a large enough fee such that the overall average fee of all three transactions is at or above market rate.  Miners may be smart enough to realize that they can earn a good overall fee by confirming all three.  This is the idea of the <a href="https://bitcoin.stackexchange.com/questions/tagged/child-pays-for-parent">child-pays-for-parent</a> scheme, though it's usually used to have a transaction pay for its immediate inputs; I don't know whether the software used by most miners would detect longer chains like this one.</p>

<p>You can also wait for a while until other nodes have forgotten the low-fee a762 transaction, and then try to replace it with a higher-fee transaction (a double spend).  The details of doing this depend on your wallet; often it involves "zapping transactions" or "resetting blockchain" so that the wallet forgets what transactions it created, and scans the blockchain to find only those which are confirmed.  If other nodes have also forgotten the unconfirmed transaction, then it's as if they never happened and you can start again.</p>

CC BY-SA 3.0
2017-06-15T06:41:47.057Z
Thanks for the answer Nate! I woke up this morning, finding that my latest transaction had gone through, after reading your reply, which surprised me. Now I see that also the previous transaction, which was stuck for about 2 weeks also was confirmed. The transaction fees of both transactions combined, must have been sufficient to be processed, but as the average fee was a bit low, it was probably delayed like that. Luckily a third transaction was not required to push the others trough.
Richard
CC BY-SA 3.0
2017-06-14T22:43:58.237Z
2017-06-14T22:43:58.237Z
Nate Eldredge
<ol>
<li><p>I have started a <a href="https://blockchain.info/tx/7da905ff2f82ac9307cdea917e126246ddb640a4c37025af6262ca398b9de86a" rel="nofollow noreferrer">transaction</a> from "wallet A" at <code>2017-06-14 11:51:40</code> with </p>

<blockquote>
  <p>Fees <code>0.00066328 BTC</code>,
  Fee per byte <code>293.487 sat/B</code></p>
</blockquote>

<p>Which is not yet confirmed over 8 hours later. </p></li>
<li><p>I have a second <a href="https://blockchain.info/tx/ec561ce683921809ebf8853cba8303c0852d5d4849920ef7116bbb15237ec3c9" rel="nofollow noreferrer">transaction</a> from "wallet B" at <code>2017-06-14 18:08:25</code> with </p>

<blockquote>
  <p>Fees <code>0.000599 BTC</code>,
  Fee per byte <code>265.044 sat/B</code></p>
</blockquote>

<p>Which was started almost 8 hours later than the first, with less Satoshi per byte and was confirmed within approx 1 hour. </p></li>
</ol>

<p>How can the first transaction, with a higher fee not be processed, while the second one is? I know I didn't choose the highest fee, but the selected fee should have processed the transaction within 3 blocks, which was supposed to be within 60 minutes according to <a href="https://bitcoinfees.21.co/" rel="nofollow noreferrer">https://bitcoinfees.21.co/</a>.</p>

<p><strong>Edit:</strong></p>

<p>I do have a <a href="https://blockchain.info/tx/a762746aab9daa5fc32567c1d67cd82a752570464b5dcaf9c6c2c668e36b7619" rel="nofollow noreferrer">past unconfirmed transaction</a>, for which I put a way too low transaction fee, on that wallet. If there is a previous unconfirmed transaction, does that mean the next transactions will wait for the unconfirmed transaction to complete? This will never happen...</p>

<unconfirmed-transactions>
Bitcoin transaction unconfirmed, while way past expected processing time
Richard
# Bitcoin transaction unconfirmed, while way past expected processing time

(Asked by: username_0 on 2017-06-14)

1. I have started a [transaction](https://blockchain.info/tx/7da905ff2f82ac9307cdea917e126246ddb640a4c37025af6262ca398b9de86a) from "wallet A" at `2017-06-14 11:51:40` with

   > Fees `0.00066328 BTC`,
   > Fee per byte `293.487 sat/B`

   Which is not yet confirmed over 8 hours later.
2. I have a second [transaction](https://blockchain.info/tx/ec561ce683921809ebf8853cba8303c0852d5d4849920ef7116bbb15237ec3c9) from "wallet B" at `2017-06-14 18:08:25` with

   > Fees `0.000599 BTC`,
   > Fee per byte `265.044 sat/B`

   Which was started almost 8 hours later than the first, with less Satoshi per byte and was confirmed within approx 1 hour.

How can the first transaction, with a higher fee not be processed, while the second one is? I know I didn't choose the highest fee, but the selected fee should have processed the transaction within 3 blocks, which was supposed to be within 60 minutes according to <https://bitcoinfees.21.co/>.

**Edit:**

I do have a [past unconfirmed transaction](https://blockchain.info/tx/a762746aab9daa5fc32567c1d67cd82a752570464b5dcaf9c6c2c668e36b7619), for which I put a way too low transaction fee, on that wallet. If there is a previous unconfirmed transaction, does that mean the next transactions will wait for the unconfirmed transaction to complete? This will never happen...

**Tags:** unconfirmed-transactions


---

## 1 answers

### Answer by username_1 on 2017-06-14. Score: 2 | Accepted answer

That's correct, a transaction cannot be confirmed until all its inputs (and all of their inputs, and so on) have confirmed. (It is allowed for the transaction to go in the same block as its inputs, so that they confirm simultaneously.)

You may be able to remedy the situation by creating a third transaction that spends the second (7da9), with a large enough fee such that the overall average fee of all three transactions is at or above market rate. Miners may be smart enough to realize that they can earn a good overall fee by confirming all three. This is the idea of the [child-pays-for-parent](https://bitcoin.stackexchange.com/questions/tagged/child-pays-for-parent) scheme, though it's usually used to have a transaction pay for its immediate inputs; I don't know whether the software used by most miners would detect longer chains like this one.

You can also wait for a while until other nodes have forgotten the low-fee a762 transaction, and then try to replace it with a higher-fee transaction (a double spend). The details of doing this depend on your wallet; often it involves "zapping transactions" or "resetting blockchain" so that the wallet forgets what transactions it created, and scans the blockchain to find only those which are confirmed. If other nodes have also forgotten the unconfirmed transaction, then it's as if they never happened and you can start again.

> **Comments:**
> **username_0**: Thanks for the answer username_1! I woke up this morning, finding that my latest transaction had gone through, after reading your reply, which surprised me. Now I see that also the previous transaction, which was stuck for about 2 weeks also was confirmed. The transaction fees of both transactions combined, must have been sufficient to be processed, but as the average fee was a bit low, it was probably delayed like that. Luckily a third transaction was not required to push the others trough.  

---

