RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

OMOCHI RPC endpoints

Chain ID 2mBbfPEFbdEqeaBvRLgvmQQA3cG5mbpqbC8fcXCTZaycXZrXDqnet: mainnettype: chainkind: avax_subnet
Wallet RPC URLhttps://omochi.rpcscan.xyz
Open
Overview
Native coin
-
Chain ID
-
Aliases
-
Net
mainnet
Type
chain
VM
avax_subnet
Multichain Info?(EIP-7930?)
Namespace?
CAIP-2?
avalanche:2mBbfPEFbdEqeaBvRLgvmQQA3cG5mbpqbC8fcXCTZaycXZrXDq
CAIP-350?
avalanche:2mBbfPEFbdEqeaBvRLgvmQQA3cG5mbpqbC8fcXCTZaycXZrXDq
ChainType?
-
ChainReference?
-
Reference: EIP-7930 · CAIP-350 · CAIP-2 · Glossary
RPC URLs (1)
SchemeURLPostureSpeed
HTTPS
https://subnets.avax.network/omochi/mainnet/rpc
BA+details →
Get Fastest (live race)
method eth_chainId() from your browser · timeout 6s

Races every HTTPS endpoint on OMOCHI with a real JSON-RPC POST from your browser. Sorted by the actual latency you’re seeing right now. Requests leave your machine, not RPCScan servers.

Consensus & Algorithm
Mechanism
-
Algorithm
-
Hash funcs
-
Masternode
-
Economics
Max supply
-
Total supply
-
Circulating
-
Premine
-
Block reward
-
Inflation
-
Avg tx fee
-