<pre><code>$ src/bitcoin-cli getmempoolentry ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e
{
  &quot;fees&quot;: {
    &quot;base&quot;: 0.00012042,
    &quot;modified&quot;: 0.00012042,
    &quot;ancestor&quot;: 0.00125452,
    &quot;descendant&quot;: 0.00012042
  },
  &quot;vsize&quot;: 224,
  &quot;weight&quot;: 896,
  &quot;fee&quot;: 0.00012042,
  &quot;modifiedfee&quot;: 0.00012042,
  &quot;time&quot;: 1612178927,
  &quot;height&quot;: 668604,
  &quot;descendantcount&quot;: 1,
  &quot;descendantsize&quot;: 224,
  &quot;descendantfees&quot;: 12042,
  &quot;ancestorcount&quot;: 2,
  &quot;ancestorsize&quot;: 22989,
  &quot;ancestorfees&quot;: 125452,
  &quot;wtxid&quot;: &quot;ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e&quot;,
  &quot;depends&quot;: [
    &quot;fb1183fa83759c51bd33d2bad9007804ea44f8256a7ae77f36f4f35a885a05d6&quot;
  ],
  &quot;spentby&quot;: [
  ],
  &quot;bip125-replaceable&quot;: false,
  &quot;unbroadcast&quot;: false
}
</code></pre>
<p>Looks like your transaction depends on another unconfirmed transaction, and that transaction is large and has a low feerate.  The combined feerate of the two transactions is only around 5.45sat/vB, which presumably explains the long time to confirm.</p>

CC BY-SA 4.0
2021-02-04T18:30:32.720Z
2021-02-04T18:30:32.720Z
sdaftuar
<p>I was sent a transaction that has been unconfirmed for 3 days now - but the feerate is relatively high (53.8 sat/vB). Blocks have been confirming transactions with lower feerates for days, but for some reason skip over mine. For example, last night there were whole blocks of transactions &lt; 50sat/vB, but for some reason they skipped over mine (ex: <a href="https://mempool.space/block/00000000000000000006e91bfcee72653533739b834f56c550405862508883f1" rel="nofollow noreferrer">https://mempool.space/block/00000000000000000006e91bfcee72653533739b834f56c550405862508883f1</a>).</p>
<p>My Tx: ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e</p>
<p>I also see other unconfirmed transactions with high fees (<a href="https://blockchair.com/bitcoin/mempool/transactions?q=fee_per_kb_usd(17..40)&amp;s=time(asc)#" rel="nofollow noreferrer">https://blockchair.com/bitcoin/mempool/transactions?q=fee_per_kb_usd(17..40)&amp;s=time(asc)#</a>) some that have been waiting for weeks.</p>
<p>Is there a technical reason as to why miners are skipping over transactions like these?</p>
<p>Thanks!</p>

<transaction-fees><unconfirmed-transactions><transaction-selection><child-pays-for-parent>
Transaction with a high fee keeps getting skipped... Reason why?
user115073
# Transaction with a high fee keeps getting skipped... Reason why?

(Asked by: username_0 on 2021-02-04)

I was sent a transaction that has been unconfirmed for 3 days now - but the feerate is relatively high (53.8 sat/vB). Blocks have been confirming transactions with lower feerates for days, but for some reason skip over mine. For example, last night there were whole blocks of transactions < 50sat/vB, but for some reason they skipped over mine (ex: <https://mempool.space/block/00000000000000000006e91bfcee72653533739b834f56c550405862508883f1>).

My Tx: ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e

I also see other unconfirmed transactions with high fees (<https://blockchair.com/bitcoin/mempool/transactions?q=fee_per_kb_usd(17..40)&s=time(asc)#>) some that have been waiting for weeks.

Is there a technical reason as to why miners are skipping over transactions like these?

Thanks!

**Tags:** transaction-fees, unconfirmed-transactions, transaction-selection, child-pays-for-parent


---

## 1 answers

### Answer by username_1 on 2021-02-04. Score: 4 | Accepted answer

```
$ src/bitcoin-cli getmempoolentry ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e
{
  "fees": {
    "base": 0.00012042,
    "modified": 0.00012042,
    "ancestor": 0.00125452,
    "descendant": 0.00012042
  },
  "vsize": 224,
  "weight": 896,
  "fee": 0.00012042,
  "modifiedfee": 0.00012042,
  "time": 1612178927,
  "height": 668604,
  "descendantcount": 1,
  "descendantsize": 224,
  "descendantfees": 12042,
  "ancestorcount": 2,
  "ancestorsize": 22989,
  "ancestorfees": 125452,
  "wtxid": "ed45c837d26c25fb6a763708376a87f1875ff57efbb0f56d1b26d00a16c1899e",
  "depends": [
    "fb1183fa83759c51bd33d2bad9007804ea44f8256a7ae77f36f4f35a885a05d6"
  ],
  "spentby": [
  ],
  "bip125-replaceable": false,
  "unbroadcast": false
}

```

Looks like your transaction depends on another unconfirmed transaction, and that transaction is large and has a low feerate. The combined feerate of the two transactions is only around 5.45sat/vB, which presumably explains the long time to confirm.


---

