Main.netChain settings lookup

Chain profile

Injective EVM chain ID 1776 and mainnet RPC URL

Reviewed

Checked June 26, 2026. Injective publishes EVM network information for its mainnet EVM layer. Injective documentation lists chain ID 1776, JSON-RPC endpoint, and Blockscout explorer.

Chain ID1776 / 0x6f0
RPC URLhttps://sentry.evm-rpc.injective.network
Explorerhttps://blockscout.injective.network
Gas tokenINJ
VerificationVerified metadata
Manual reviewJune 26, 2026
Evidence snapshot

Verification record

Manual metadata review and automated evidence checks are tracked separately. This is not a live uptime, latency, or production reliability monitor.

Manual metadata review
Verification status
Verified metadata
Verification run
source-monitoring-2026-06-26
Verification tool
source-monitoring-refresh
Source set
Injective docs
Manual review cadence
monthly; after July 26, 2026
Latest recorded chain ID probe
eth_chainId matched expected 0x6f0; observed 0x6f0 on

MethodologyReport a correction

Injective EVM wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same setup fields as text so developers can compare them with official/source docs before callingwallet_addEthereumChain.

chainId
0x6f0 (1776)
chainName
Injective EVM
nativeCurrency
INJ; name INJ, symbol INJ, decimals 18
rpcUrls
https://sentry.evm-rpc.injective.network
blockExplorerUrls
https://blockscout.injective.network
GlossaryChain IDHow wallet and RPC software identify a mainnet network.GlossaryRPC endpointWhat an RPC URL does and why public endpoints can be rate-limited.GlossaryMainnetThe production network context for these chain settings.Gas tokenINJ gas tokenOther mainnet rows that use INJ for gas.Network categoryEVM mainnetsCompare Injective EVM with related evm mainnets by chain ID, RPC URL, explorer, and source links.Network categoryL1 mainnetsCompare Injective EVM with related l1 mainnets by chain ID, RPC URL, explorer, and source links.GuideChain ID listChain IDs, RPC URLs, explorers, and source links across Main.net.

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims.

Snapshot generated
Source checks
1 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0x6f0
Per-source check timing
Included in the monitoring snapshot, not used as this page's review date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC
https://sentry.evm-rpc.injective.network
Explorer
https://blockscout.injective.network
Official/source documentation
Injective docs
Chain type
EVM L1 mainnet
Chain ID hex
0x6f0
Manual review cadence
monthly; next review after July 26, 2026

Injective EVM common questions

What is the Injective EVM mainnet RPC URL?
Injective EVM's listed primary public RPC URL is https://sentry.evm-rpc.injective.network.
What is Injective EVM's chain ID?
Injective EVM's listed chain ID is 1776.
What block explorer does Injective EVM use?
Injective EVM's listed block explorer is https://blockscout.injective.network.
What gas token does Injective EVM use?
Injective EVM's listed gas token is INJ.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal1776
Chain ID hex0x6f0
RPC URLhttps://sentry.evm-rpc.injective.network
Explorer URLhttps://blockscout.injective.network
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x6f0",
  "chainName": "Injective EVM",
  "nativeCurrency": {
    "name": "INJ",
    "symbol": "INJ",
    "decimals": 18
  },
  "rpcUrls": [
    "https://sentry.evm-rpc.injective.network"
  ],
  "blockExplorerUrls": [
    "https://blockscout.injective.network"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

ts

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const injectiveEvmMainnet = defineChain({
  id: 1776,
  name: "Injective EVM",
  nativeCurrency: {
    name: "INJ",
    symbol: "INJ",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://sentry.evm-rpc.injective.network"] },
    public: { http: ["https://sentry.evm-rpc.injective.network"] },
  },
  blockExplorers: {
    default: {
      name: "blockscout.injective.network",
      url: "https://blockscout.injective.network",
    },
  },
})
ts

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { injectiveEvmMainnet } from './injective-evm'

export const config = createConfig({
  chains: [injectiveEvmMainnet],
  transports: {
    [injectiveEvmMainnet.id]: http("https://sentry.evm-rpc.injective.network"),
  },
})
ts

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://sentry.evm-rpc.injective.network", {
  chainId: 1776,
  name: "injective-evm",
})

const network = await provider.getNetwork()
console.log(network.chainId)
bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://sentry.evm-rpc.injective.network

# Expected chain ID: 1776 / 0x6f0

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

explorerInjective EVM explorerExplorer-hosted blocks, transactions, contracts, token transfers, and verification tools from the listed explorer.

Source links

Injective EVM network information

Safety note

Injective documentation notes that native Injective uses injective-1 while the EVM layer uses numeric chain ID 1776. Use the numeric ID for EVM tooling.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report Injective EVM dataSend page feedback