Supported Networks
You can find our currently supported networks and products for each network below. Blocknative constantly adds new networks and product support for those networks.
Blocknative products support the below networks at various levels. Mempool Explorer and web3-onboard work with any networks with Core support. For details on each feature under the networks, please see the Feature Details section.
Network Id: 1
- Core
- Decode
- Replace
- Trace
- Revert
- Simulation Platform
- Gas Platform
- MEV Bundle RPC Endpoint
- MEV Relay
Network Id: 5
- Core
- Decode
- Replace
- Trace
- Revert
- Simulation Platform
- Gas Platform
- MEV Bundle RPC Endpoint
- MEV Relay
Network Id: 100
- Core
- Decode
- Replace
- Trace
- Revert
- Simulation Platform
- Gas Platform
Network Id: 137
- Core
- Decode
- Replace
- Trace
- Revert
- Simulation Platform
- Gas Platform
Network Id: 80001
- Core
- Decode
- Replace
- Trace
- Revert
- Simulation Platform
- Gas Platform
Descriptions of the feature areas identified in Chain Feature Support summary table.
Core notifications include the basic detection of entry into mempool (
pending
) and addition to chain (confirmed
, failed
). Watching an address will only receive core notifications if the address is the from
or to
field in the transaction.Decoding enables inspection of the
input
field for contract calls, either automatically or via user input of ABI. Watching an address that is part of the input
parameters to the contract will trigger relevant core notifications. Notification payloads will include the contractCall
structure.Replacement notifications include
speedup
and cancel
. A watched transaction will receive a notification when that transaction is replaced and the notification will include a reference to the replacing tx.Notify automatically switch the watched transaction to the replacement so further state changes can be notified.
Tracing enables inspection of the internal calls of finalized transactions (
confirmed
, failed
). Watching an address that is part of an internal call, but not an address in the from
or to
fields, will receive finalized state notifications and the payload will include the internalTransactions
structure.If a watched address is in the
from
or to
field, a core notification is sent, but no trace notification is sent since each transaction state is sent only once to each receiver.Revert enables determination of the reason message for
failed
transactions. Watching a transaction, or the transactions of a watched address, will include a value in the reason
field for failed
transactions if a value exists (i.e. is output by the contract after EVM execution).Simulation platform enables inspection of internal calls of
pending
transactions. Watching an address that is part of an internal call, but not an address in the from
or to
fields, will receive pending-simulation
notifications and the payload will include the internalTransactions
structure.pending-simulation
notifications are delivered in addition to any of the other notifications. For example, users can receive both pending
and pending-simulation
notifications.Gas platform provides a feed of the distribution of gas prices in the mempool and a payload based on a predictive model of gas prices for confirmation in the next block. For more information please visit Gas Platform docs.
Last modified 6mo ago