Documentation

Nexis Chain is chain ID 5567, EVM-compatible, and speaks standard Ethereum JSON-RPC — any Ethereum tooling (Hardhat, Foundry, viem, ethers.js, MetaMask) works against it unmodified.

This explorer exposes two ways to read chain data: a read-only REST API for indexed, queryable history (blocks, transactions, token transfers…), and the raw JSON-RPC endpoint for live node state and submitting transactions.

Nexis Chain runs a geth-based Clique proof-of-authority chain — blocks are signed by a fixed, known set of validators rather than mined, so finality is fast and gas stays predictable. Consensus is currently served by a dual-validator setup for redundancy.

Click Connect in the header to link a browser wallet, or add the network manually from the RPC page — it has a one-click "Add to Wallet" button that fills in the RPC URL and chain ID for you.

Because validators are permissioned under Clique, block signing is not open to arbitrary miners — this only affects block production, not wallet connection or transaction submission, which work exactly like any other EVM chain.

For anything historical or aggregated — a paginated list of an address's transactions, token balances, the richlist — use the REST API. It's the same API this explorer's own pages call, so response shapes are guaranteed to stay in sync with what you see rendered.

curl "https://nexischain.com/explorer/api/address/0xabc.../transactions?limit=10"

For live node state (pending nonce, current gas price) or to submit a signed transaction, call the JSON-RPC endpoint directly with any standard Ethereum method.

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  chain: { id: 5567, name: "Nexis Chain" },
  transport: http("https://rpc.nexischain.com"),
});

const block = await client.getBlockNumber();

Common methods work as expected: eth_getBalance, eth_call, eth_estimateGas, eth_sendRawTransaction. Always sign transactions locally and broadcast the raw hex — never send a private key to any RPC endpoint.

Assets move in and out of Nexis Chain through purpose-built bridge contracts rather than a single generic gateway:

• Buy NXC — acquire the native token directly.
• NXC ⇄ USDT Bridge — move value between Nexis Chain and USDT.
• G20 ⇄ USDT Bridge — move value between the G20 token and USDT.

Bridge transactions settle on both chains independently — confirm finality on the destination chain before treating funds as available, the same way you would with any cross-chain transfer.

GlobalStaken is the ecosystem's DeFi protocol, running on Nexis Chain and reachable at globalstaken.io. Contract addresses referenced from GlobalStaken can be looked up and verified the same way as any other address on this explorer.

Publish your single-file Solidity source from the contract's address page, or start from Verify Contract. Match the compiler version, optimizer runs, and EVM version to exactly what you built with — verification compares compiled bytecode byte-for-byte against what's deployed.

Calling a contract off-chain (e.g. via eth_call or eth_sendRawTransaction) means encoding a function signature and its arguments into calldata yourself. Use the ABI Encoder to do that (and the reverse) without leaving the browser.

Transaction stuck pending — under Clique PoA, blocks are only produced by the active validator set; a stall usually means checking the RPC endpoint's current block height against the explorer rather than resubmitting.

Wrong nonce / replaced tx — fetch the latest pending nonce with eth_getTransactionCount using the "pending" block tag, not "latest", if you're sending multiple transactions in quick succession.

Verification mismatch — double-check compiler version, optimizer setting, and optimizer runs; a byte-for-byte bytecode match is required, so even a metadata hash difference will fail it.