> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/blocknative.md).

# Blocknative

Blocknative mempool monitoring and gas estimation tools for Chiliz Chain, delivering 600+ gas price estimates per second via the Gas Network.

## What is Blocknative?

[Blocknative](https://www.blocknative.com/) provides real-time tools and infrastructure that monitor and manage blockchain transaction data in the mempool (where pending transactions wait before being included in a new block on the blockchain).

## What this means for you

Blocknative delivers over 600 gas estimates per second, through the [Gas Network](https://gas.network/).

Blocknative offers:

* Gas Fee Estimation
* Gas Prediction
* Gas Estimator
* Mempool Monitoring

Among other tools, you can use their Gas Price API to obtain the gas price needed to have a certain probability to qualify for inclusion in the next block (for Ethereum or Bitcoin) or the next ∼10 seconds, depending on the chain.

### Use Blocknative with Chiliz Chain

Check out this short how-to to estimate gas fees for your project:

{% content-ref url="/pages/mo6ugHFstOifHecV3GHi" %}
[Estimate gas fees](/develop/advanced/estimate-gas-fees.md)
{% endcontent-ref %}

And see all the chains that Blocknative supports:

{% embed url="<https://docs.blocknative.com/gas-prediction/gas-platform>" %}

Explore Blocknative further with their documentation:

{% embed url="<https://docs.blocknative.com/>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/blocknative.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.