<p>According to <a href="https://transactionfee.info/charts/transactions-signaling-explicit-rbf/" rel="nofollow noreferrer">https://transactionfee.info/charts/transactions-signaling-explicit-rbf/</a>, ~27% of transactions have signaled for RBF.</p>
<p>Bitcoin Core does not record this information by itself. You will need to compute the statistic yourself by inspecting each transaction. This can be achieved using the <code>getblock</code> RPC to get a block, then you would need to inspect each transaction and see if any input's sequence number is less than or equal to <code>0xfffffffd</code>.</p>

CC BY-SA 4.0
2022-08-14T05:21:19.707Z
0xfffffffd or 0xfffffffe?
bordalix
CC BY-SA 4.0
2022-08-14T07:22:02.453Z
@bordalix `<= 0xfffffffd`. `0xfffffffe` was kept as a non-signaling value to allow opting in to `nLockTime` without opting to RBF signaling.
Antoine Poinsot
CC BY-SA 4.0
2022-08-13T23:09:16.997Z
2022-08-13T23:09:16.997Z
Ava Chow
<p>What's the percentage of on-chain transactions having RBF (replace-by-fee) activated the last 30 days?</p>
<p>What query could I run against my node to find out?</p>

<replace-by-fee><statistics>
Where can I find statistics for the current RBF adoption?
Paul
# Where can I find statistics for the current RBF adoption?

(Asked by: username_0 on 2022-08-13)

What's the percentage of on-chain transactions having RBF (replace-by-fee) activated the last 30 days?

What query could I run against my node to find out?

**Tags:** replace-by-fee, statistics


---

## 1 answers

### Answer by username_1 on 2022-08-13. Score: 2 | Accepted answer

According to <https://transactionfee.info/charts/transactions-signaling-explicit-rbf/>, ~27% of transactions have signaled for RBF.

Bitcoin Core does not record this information by itself. You will need to compute the statistic yourself by inspecting each transaction. This can be achieved using the `getblock` RPC to get a block, then you would need to inspect each transaction and see if any input's sequence number is less than or equal to `0xfffffffd`.

> **Comments:**
> **username_2**: 0xfffffffd or 0xfffffffe?  
> **username_3**: @username_2 `<= 0xfffffffd`. `0xfffffffe` was kept as a non-signaling value to allow opting in to `nLockTime` without opting to RBF signaling.  

---

