<p>Your transaction paid a fee of 1674 satoshis for 372 bytes, or a fee rate of 4.5 satoshis per byte, which was a reasonable estimate in the past hour (via <a href="https://mempool.space/tv" rel="noreferrer">https://mempool.space/tv</a>):<a href="https://i.sstatic.net/B0Caf.png" rel="noreferrer"><img src="https://i.sstatic.net/B0Caf.png" alt="enter image description here"></a></p>

<p>There was just a slow block with #600,283 taking 37 minutes to be found (via <a href="https://blockchair.com" rel="noreferrer">https://blockchair.com</a>) and it looks like your transaction would have been exactly in that little blue corner above the dotted line.</p>

<p><a href="https://i.sstatic.net/8D75z.png" rel="noreferrer"><img src="https://i.sstatic.net/8D75z.png" alt="enter image description here"></a></p>

<p>Otherwise, four of the last six blocks were not even full, so if not for that slower block, it would have been included in the next block (via <a href="https://mempool.space/tv" rel="noreferrer">https://mempool.space/tv</a>):
<a href="https://i.sstatic.net/x7pYH.png" rel="noreferrer"><img src="https://i.sstatic.net/x7pYH.png" alt="overview of last six blocks"></a></p>

<p>Should you do get a transaction stuck during a congestion phase sometime in the future, check out this canonical question: <a href="https://bitcoin.stackexchange.com/q/9046/5406">Why is my transaction not getting confirmed and what can I do about it?</a></p>

CC BY-SA 4.0
2019-10-21T00:14:57.803Z
2019-10-21T02:07:43.683Z
2019-10-21T02:07:43.683Z
Murch
<p>The hourly average fee when this question was posted was between 9 and 10 Satoshi per Byte (sat/B).</p>

<p>The latest TX's that I just <a href="https://www.blockchain.com/btc/block/0000000000000000000e1d4ce08cb39bc27f705ea89347c8c8b4694cdcdf20bb" rel="noreferrer">randomly checked</a> all had 10.03 sat/B fee which is higher than the 4.5 sat/B that you sent.</p>

<p>Transactions are <a href="https://www.blockchain.com/en/charts/mempool-size" rel="noreferrer">at a hourly peak right now</a>. Wait it out and it'll probably go through in the next couple of hours as the mempool empties.</p>

<p>I just noticed your TX went through and has 3 confirmations from the time I started replying to now. So I guess this is a closed issue.</p>

CC BY-SA 4.0
2019-10-21T00:16:46.247Z
Since transactions can be of different size, miners actually select transactions by fee rate (fee over size), not by absolute fees.
Murch
CC BY-SA 4.0
2019-10-21T00:22:37.310Z
@Murch Yep. His was 4.5 sat/B and those I checked (the first few on that block I linked to) all were 10.xx sat/B.
Jose Fonseca
CC BY-SA 4.0
2019-10-21T00:31:38.840Z
Block #600283 had 18 transactions with fee rates below 3 sats/B, but that's not my point. The point I was trying to make was that the absolute fee a transaction paid is not a good metric to assess its priority, because paying 2200 sats for a 1100 byte transaction is a lower fee rate than paying 1674 satoshis for a 372 byte transaction.
Murch
CC BY-SA 4.0
2019-10-21T01:10:12.677Z
@Murch OK, thanks for the suggestion I've reworded the answer. Let me know please if this is better.
Jose Fonseca
CC BY-SA 4.0
2019-10-20T23:54:25.747Z
2019-10-21T01:09:46.483Z
2019-10-21T01:09:46.483Z
Jose Fonseca
<p>I recently sent btc that appears to be stuck (<a href="https://live.blockcypher.com/btc/tx/c131d65d933e343f852021830b833123de952c1857f264503388cf642655c457/" rel="nofollow noreferrer">https://live.blockcypher.com/btc/tx/c131d65d933e343f852021830b833123de952c1857f264503388cf642655c457/</a>)</p>

<p>The interesting thing is that I used a higher fee (4.5 sat/byte) which was the highest fee that Electrum's slider would support. I also notice that there are only two transactions in this block. Did I screw up? Is there any way that I can fix this?</p>

<p>Edit: Electrum says that I am only 0.12 MB from tip, however it has hovered around there without moving and sometimes increasing in size.</p>

<transactions><transaction-fees><unconfirmed-transactions><electrum>
Transaction with highest fee, but stuck, what did I do wrong?
Jacob M.
# Transaction with highest fee, but stuck, what did I do wrong?

(Asked by: username_0 on 2019-10-20)

I recently sent btc that appears to be stuck (<https://live.blockcypher.com/btc/tx/c131d65d933e343f852021830b833123de952c1857f264503388cf642655c457/>)

The interesting thing is that I used a higher fee (4.5 sat/byte) which was the highest fee that Electrum's slider would support. I also notice that there are only two transactions in this block. Did I screw up? Is there any way that I can fix this?

Edit: Electrum says that I am only 0.12 MB from tip, however it has hovered around there without moving and sometimes increasing in size.

**Tags:** transactions, transaction-fees, unconfirmed-transactions, electrum


---

## 2 answers

### Answer by username_2 on 2019-10-20. Score: 6 | Accepted answer

The hourly average fee when this question was posted was between 9 and 10 Satoshi per Byte (sat/B).

The latest TX's that I just [randomly checked](https://www.blockchain.com/btc/block/0000000000000000000e1d4ce08cb39bc27f705ea89347c8c8b4694cdcdf20bb) all had 10.03 sat/B fee which is higher than the 4.5 sat/B that you sent.

Transactions are [at a hourly peak right now](https://www.blockchain.com/en/charts/mempool-size). Wait it out and it'll probably go through in the next couple of hours as the mempool empties.

I just noticed your TX went through and has 3 confirmations from the time I started replying to now. So I guess this is a closed issue.

> **Comments:**
> **username_1**: Since transactions can be of different size, miners actually select transactions by fee rate (fee over size), not by absolute fees.  
> **username_2**: @username_1 Yep. His was 4.5 sat/B and those I checked (the first few on that block I linked to) all were 10.xx sat/B.  
> **username_1**: Block #600283 had 18 transactions with fee rates below 3 sats/B, but that's not my point. The point I was trying to make was that the absolute fee a transaction paid is not a good metric to assess its priority, because paying 2200 sats for a 1100 byte transaction is a lower fee rate than paying 1674 satoshis for a 372 byte transaction.  
> **username_2**: @username_1 OK, thanks for the suggestion I've reworded the answer. Let me know please if this is better.  

---

### Answer by username_1 on 2019-10-21. Score: 5

Your transaction paid a fee of 1674 satoshis for 372 bytes, or a fee rate of 4.5 satoshis per byte, which was a reasonable estimate in the past hour (via <https://mempool.space/tv>):[![enter image description here](https://i.sstatic.net/B0Caf.png)](https://i.sstatic.net/B0Caf.png)

There was just a slow block with #600,283 taking 37 minutes to be found (via <https://blockchair.com>) and it looks like your transaction would have been exactly in that little blue corner above the dotted line.

[![enter image description here](https://i.sstatic.net/8D75z.png)](https://i.sstatic.net/8D75z.png)

Otherwise, four of the last six blocks were not even full, so if not for that slower block, it would have been included in the next block (via <https://mempool.space/tv>):
[![overview of last six blocks](https://i.sstatic.net/x7pYH.png)](https://i.sstatic.net/x7pYH.png)

Should you do get a transaction stuck during a congestion phase sometime in the future, check out this canonical question: [Why is my transaction not getting confirmed and what can I do about it?](https://bitcoin.stackexchange.com/q/9046/5406)


---

