<p>It is 1343 bytes, larger than 1000 bytes, so you should have paid 0.2mBTC.</p>

<p>You have too many inputs in this transactions. If you had used a compressed public key, you might be able to save some bytes and shrink the transaction size down to under 1kB.</p>

CC BY-SA 3.0
2014-03-12T16:03:04.150Z
2014-03-12T16:03:04.150Z
uminatsu
<p>Why does Blockchain.info refer to <a href="https://blockchain.info/tx/ff003a7ca895c3eb7148861ebb200551a310a71c99d50d5f69147969e91e08ee" rel="nofollow">this</a> transaction as "low fee", when it has the normal fee? What is wrong with it? Its size is less than 1000 bytes, with a fee of 0.1 mBTC – yet, this transaction just got stuck?</p>

<p>Could anyone please explain please what happened and why it got stuck?</p>

CC BY-SA 3.0
2014-03-12T09:21:20.783Z
Finally it confirmed. But confirmation time for only one confirmation took almost 24 hours. I never faced case like this before.
Arsenius
<transactions><transaction-fees>
Why is this transaction referred to as "low fee"?
Arsenius
# Why is this transaction referred to as "low fee"?

(Asked by: username_0 on 2014-03-12)

Why does Blockchain.info refer to [this](https://blockchain.info/tx/ff003a7ca895c3eb7148861ebb200551a310a71c99d50d5f69147969e91e08ee) transaction as "low fee", when it has the normal fee? What is wrong with it? Its size is less than 1000 bytes, with a fee of 0.1 mBTC – yet, this transaction just got stuck?

Could anyone please explain please what happened and why it got stuck?

**Tags:** transactions, transaction-fees

> **Comments:**
> **username_0**: Finally it confirmed. But confirmation time for only one confirmation took almost 24 hours. I never faced case like this before.  

---

## 1 answers

### Answer by username_1 on 2014-03-12. Score: 3

It is 1343 bytes, larger than 1000 bytes, so you should have paid 0.2mBTC.

You have too many inputs in this transactions. If you had used a compressed public key, you might be able to save some bytes and shrink the transaction size down to under 1kB.


---

