<p>Bitcoin Core has updated their fee estimation logic several times in the past few years, another patch coming up shortly in Bitcoin Core 0.15.0. If you aren't running a current version of Bitcoin Core, you should first update your software to the most recent version.</p>

<p>If the problem occurred with a recent version of Bitcoin Core, you should consider checking different resources on the web to get a feeling for the current fee level on the network in order to sanity-check the fee level suggested by Bitcoin Core during the transaction generation process.</p>

<p>Some such sites are:</p>

<ul>
<li><a href="https://btc.com/stats/unconfirmed-tx" rel="nofollow noreferrer">https://btc.com/stats/unconfirmed-tx</a></li>
<li><a href="https://bitcoinfees.github.io/" rel="nofollow noreferrer">https://bitcoinfees.github.io/</a></li>
<li><a href="https://bitcoinfees.21.co/" rel="nofollow noreferrer">https://bitcoinfees.21.co/</a></li>
</ul>

<p>Another option would be to use the RBF feature, although this is currently only available for crafting transactions via commandline. A pullrequest to support it in the GUI is in the makings, I think that Bitcoin Knots (Luke Dashjr's client) already supports it in the GUI.</p>

CC BY-SA 3.0
2017-05-24T17:59:13.457Z
2017-05-24T18:04:49.807Z
2017-05-24T18:04:49.807Z
Murch
<p>Probably this is because you set the fee in BTC/KB but your transaction is usually less than 1KB in size. If you use <code>Fee/KB = fee / (transaction size in Bytes / 1000)</code> then you should probably see that the fee on the transaction is what you have set.</p>

CC BY-SA 3.0
2018-01-28T03:03:05.817Z
2018-01-28T03:03:05.817Z
Willtech
<p>I have the same problem with unconfirmed transaction and I already know how to solve it. But I don't know how to define transaction fee so that it doesn't happen again. I'm using the Bitcoin Core wallet and I chose the recommended option for transaction and fastest confirmation time. When I sent the transaction, a lower fee was applied than recommended and now the status of transaction is: 0/unconfirmed, in memory pool, broadcast through 1 node(s). </p>

<bitcoin-core><transaction-fees><unconfirmed-transactions>
How do you choose the correct fee with Bitcoin Core?
Vol
# How do you choose the correct fee with Bitcoin Core?

(Asked by: username_0 on 2017-05-24)

I have the same problem with unconfirmed transaction and I already know how to solve it. But I don't know how to define transaction fee so that it doesn't happen again. I'm using the Bitcoin Core wallet and I chose the recommended option for transaction and fastest confirmation time. When I sent the transaction, a lower fee was applied than recommended and now the status of transaction is: 0/unconfirmed, in memory pool, broadcast through 1 node(s).

**Tags:** bitcoin-core, transaction-fees, unconfirmed-transactions


---

## 2 answers

### Answer by username_1 on 2017-05-24. Score: 2 | Accepted answer

Bitcoin Core has updated their fee estimation logic several times in the past few years, another patch coming up shortly in Bitcoin Core 0.15.0. If you aren't running a current version of Bitcoin Core, you should first update your software to the most recent version.

If the problem occurred with a recent version of Bitcoin Core, you should consider checking different resources on the web to get a feeling for the current fee level on the network in order to sanity-check the fee level suggested by Bitcoin Core during the transaction generation process.

Some such sites are:

* <https://btc.com/stats/unconfirmed-tx>
* <https://bitcoinfees.github.io/>
* <https://bitcoinfees.21.co/>

Another option would be to use the RBF feature, although this is currently only available for crafting transactions via commandline. A pullrequest to support it in the GUI is in the makings, I think that Bitcoin Knots (Luke Dashjr's client) already supports it in the GUI.


---

### Answer by username_2 on 2018-01-28. Score: 0

Probably this is because you set the fee in BTC/KB but your transaction is usually less than 1KB in size. If you use `Fee/KB = fee / (transaction size in Bytes / 1000)` then you should probably see that the fee on the transaction is what you have set.


---

