Skip to main content
Gnosis Chain ethers.js subscription equivalent to eth_newBlockFilter. subscribe("newBlockHeaders") allows developers to subscribe to real-time updates about new block headers on the Gnosis Chain; the application will receive notifications whenever a new block is added to the blockchain. The notification will include information about the new block, such as its block number, hash, and timestamp.

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

Parameters

  • string — a keyword identifying the type of event to subscribe to, newBlockHeaders in this case.
  • function — (optional) a callback function that will be called every time a new event of the specified type is received. This function takes two parameters: error and result. The error parameter contains any error that occurred while subscribing to the event, and the result parameter contains the data for the event that was received.

Response

  • object— a block object with the following fields:
    • number — the block number of the requested block, encoded as hexadecimal. null if the block is pending.
    • hash — the block hash of the requested block. null if the block pending.
    • parenthash — hash of the previous block used to generate the current block. Also known as the ‘parent block’.
    • nonce — the hash used to demonstrate proof-of-work. null if the block pending. It returns 0x0000000000000000 when the consensus is proof-of-stake.
    • sha3uncles — the hash of the list of uncles included in the block. It is used to identify the block uniquely and to verify the integrity of the block’s data.
    • logsbloom — the bloom filter for the logs of the block, a data structure that allows for efficient membership testing of elements in a set, in this case, the logs included in the block. null if pending.
    • transactionsroot — the root of the transaction trie of the block. The transactionsRoot field allows Gnosis Chain nodes to verify the integrity of the transactions in a block.
    • stateroot — the root of the final state trie of the block. The stateroot field is included in the block header and is used to verify the integrity of the state at the time the block was processed
    • receiptsroot — the root of the receipts trie of the block. A 32-byte hash of the root node of the receipts trie of all transactions in the block. It is used to verify the integrity of the receipts data for all transactions in the block.
    • miner — the address of the miner receiving the reward.
    • difficulty — a measure of how hard it is to find a valid block for the Gnosis Chain. It is a number that increases as more miners join the network and more blocks are added to the chain, encoded as hexadecimal.
    • totaldifficulty — the cumulative sum of the difficulty of all blocks that have been mined in the Gnosis Chain network since the inception of the network. It measures the overall security and integrity of the network.
    • extradata — extra data included in a block by the miner who mined it. It often includes messages or other information related to the block.
    • size — the size of this block in bytes as an integer value, encoded as hexadecimal.
    • gaslimit — the maximum gas allowed in this block, encoded as hexadecimal.
    • gasused — the total used gas by all transactions in this block, encoded as hexadecimal.
    • timestamp — the Unix timestamp for when the block was collated.
    • transactions — an array of transaction objects. See eth_getTransactionByHash for the exact shape.
    • uncles — an array of uncle hashes.

subscribe("newBlockHeaders") code example

Note that ethers.js subscriptions require a WebSocket connection.
With ethers.js you attach a listener to the provider’s "block" event, which fires every time a new block is added to the chain. The listener receives the new block number; use provider.getBlock to fetch the full block header. You can also register a one-off "error" listener on the provider, and call provider.off("block") to stop receiving updates:
  • "block" — fires for each new block and returns the block number.
  • "error" — fires if an error is detected during the subscription.
  • provider.off("block") — removes the listener and stops the subscription.
const { ethers } = require("ethers");
const NODE_URL = "CHAINSTACK_WSS_URL";
const provider = new ethers.WebSocketProvider(NODE_URL);

async function subscribeToNewBlocks() {
    try {
        // Create a new subscription to the 'block' event
        provider.on("block", handleNewBlock);

        // Attach an event listener for any errors
        provider.on("error", handleError);
    } catch (error) {
        console.error(`Error subscribing to new blocks: ${error}`);
    }
}

/* Fallback functions to react to the different events */

// Event listener that logs the received block header data
async function handleNewBlock(blockNumber) {
    const blockHeader = await provider.getBlock(blockNumber);
    console.log(blockHeader);
}

// Event listener that logs any errors that occur
function handleError(error) {
    console.error(`Error receiving new blocks: ${error}`);
}

subscribeToNewBlocks();

Use case

A practical use case for subscribe("newBlockHeaders") is a DApp that continuously listens for new block headers, then isolates the block number and baseFeePerGas for analytics purposes. The following is an implementation of this concept using ethers.js subscriptions:
const { ethers } = require("ethers");
const NODE_URL = "CHAINSTACK_WSS_URL";
const provider = new ethers.WebSocketProvider(NODE_URL);

let blockCount = 0;

async function subscribeToNewBlocks() {
    try {
        // Create a new subscription to the 'block' event
        provider.on("block", handleNewBlock);

        // Attach an event listener for any errors
        provider.on("error", handleError);
    } catch (error) {
        console.error(`Error subscribing to new blocks: ${error}`);
    }
}

function unsubscribeFromNewBlocks() {
    provider.off("block");
    console.log("Successfully unsubscribed!");
    return process.exit(1);
}

/* Fallback functions to react to the different events */

// Event listener that extracts block number and base fee per gas from the received block header data
async function handleNewBlock(blockNumber) {

    const blockHeader = await provider.getBlock(blockNumber);
    const baseFeeGwei = ethers.formatUnits(blockHeader.baseFeePerGas, "gwei");

    blockCount++;
    console.log(`Block number: ${blockNumber} \n Base Fee per Gas: ${baseFeeGwei} Gwei \n`);
    if (blockCount === 100) {
        unsubscribeFromNewBlocks();
    }
}

// Event listener that logs any errors that occur
function handleError(error) {
    console.error(`Error receiving new blocks: ${error}`);
}

subscribeToNewBlocks();
This code creates a new subscription to the block event using the provider.on method. Registering a listener on this event lets the application react to every new block as it is added to the chain. The code defines two event listener functions that are attached to the provider: handleNewBlock and handleError. The handleNewBlock function is called when a new block is received; it fetches the full block header with provider.getBlock and extracts the block number and base fee per gas, formatting the fee with ethers.formatUnits. The handleError function is called when an error occurs, and it logs an error message. This code includes an unsubscribeFromNewBlocks function which removes the block listener with provider.off("block") and quits the program using return process.exit(1) after it received 100 new blocks. This is to demonstrate its use. Finally, the code calls the subscribeToNewBlocks function, which creates the subscription and attaches the event listeners. When a new block header is received, the handleNewBlock function is called to extract the block data and log it to the console.
Last modified on June 25, 2026