# Taxonomy of Transaction Fees in Smart Contracts

**URL:** <https://delvingbitcoin.org/t/taxonomy-of-transaction-fees-in-smart-contracts/512>\
**Category:** Protocol Design\
**Created:** [February 1, 2024, 4:50pm UTC](https://delvingbitcoin.org/t/taxonomy-of-transaction-fees-in-smart-contracts/512 "2024-02-01T16:50:52Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![instagibbs](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/instagibbs/32/28_2.png) [@instagibbs](https://delvingbitcoin.org/u/instagibbs)\
**Post date:** [February 2, 2024, 2:51pm UTC](https://delvingbitcoin.org/t/taxonomy-of-transaction-fees-in-smart-contracts/512/8 "2024-02-02T14:51:51Z")

</div>

> [@ajtowns](#):
>
> Here’s how I think I would draw them; what do you think?

I find these more confusing, but I might be alone here.

> [@jamesob](#):
>
> Just starting to read the original post; it’s not clear to me what “conflicted” with a dashed arrow means here.

An input is detected as conflicting with something in mempool, making it an RBF

---

_[View the full topic](https://delvingbitcoin.org/t/taxonomy-of-transaction-fees-in-smart-contracts/512)._