> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/ethereum-proof-of-stake-alerts-deprecated/fast-decrease-in-transaction-count-alert-deprecated.md).

# Fast Decrease in Transaction Count Alert - DEPRECATED

<mark style="color:red;">**THIS ENDPOINT HAS BEEN DEPRECATED AND WILL NO LONGER BE ACTIVELY MAINTAINED, UPDATED OR SUPPORTED**</mark>

**Alert Definition**

Alerts if the number of transactions in a block is considerably below the preceding 100 blocks.

\
**Dictionary**

| Name                                     | AlertID                         | Category | Sub-category  | Type | Unit        | Interval |
| ---------------------------------------- | ------------------------------- | -------- | ------------- | ---- | ----------- | -------- |
| Fast Decrease in Transaction Count Alert | block\_tx\_count\_rsd\_100b\_lo | Alert    | ETH PoS Alert | Sum  | Transaction | Ad hoc   |

**Interpretation**

A decrease in transaction count may be caused organically by seasonal decreases in demand, or may be a result of more concerning circumstances. If, for example, validators are censoring a specific type of transaction, blocks would not be fully empty, but transaction count would decrease.

**Potential Root Causes**

Natural drop in demand for block space, which tends to be seasonal. Potential censorship at the block producer level.

**Asset Coverage**

Ethereum (ETH)

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/ethereum-proof-of-stake-alerts-deprecated/fast-decrease-in-transaction-count-alert-deprecated.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.