Gonka mainnet · Always on

Fast, reliable RPC
for Gonka apps.

Stop worrying about overloaded public nodes. gonka RPC gives your app a dedicated, always-on gateway with full transaction history—so users never see "try again later."

Get started free See pricing

INDEX // CHAIN DATA VOLUME

Loading…

API // WHAT YOU CAN QUERY See docs

[RPC] Chain JSON-RPC Blocks, validators, ABCI

[REST] Cosmos REST API Bank, staking, tx broadcast

[TX] Transaction lookup By hash, instant

[BLOCK] Block explorer feed All txs in a height

[ADDR] Address history Full paginated tx feed

[SLASH] Slashing events Filterable by validator

[HW] Hardware registry Node registrations & snapshots

[EPOCH] Epoch performance Per-epoch counters by participant

Why teams choose gonka RPC

Always available

Public RPC nodes go down, get rate-limited, or drop under traffic. gonka RPC spreads load across a managed pool and is operated for steady uptime—not a best-effort volunteer endpoint your users depend on.

Full history, not just the tip

Most nodes are pruned: fine for "latest block," broken for "show me this wallet six months ago." Our index retains full history so explorers, support tools, and analytics work for every user—not just recent ones.

One endpoint for everything

Chain RPC, REST API, and rich indexed data (transactions, addresses, hardware, epoch metrics) behind one base URL. Change a single config line and your whole app is on gonka RPC.

Built for every use case

Wallets & apps — Send transactions and read balances without chasing which public node happens to be up. Fewer "please try again" moments for your users.

Block explorers — Look up any hash or address across the full chain history, even for blocks from months ago.

Analytics & dashboards — Pull structured data for monitoring, reporting, or internal tooling instead of rebuilding archive infrastructure yourself.

Integrators & partners — One documented endpoint for Gonka instead of maintaining a list of fragile public URLs that go stale.

Try the API — indexed lookups

Real queries against the live index. Copy any command into a terminal and run it with your API key—or get a free key first. Response times shown are typical for warm queries.

Transaction by hash

~125ms

Full transaction details by hash — ideal for explorers and support.

All transactions in a block

~110ms

Every transfer in a block height, ordered as they appeared on chain.

Address transaction history

~0.5s

Full paginated history for any wallet — sent and received, newest first.

Slashing events

~130ms

Slash records across the chain — filter by validator and height range.

Hardware node registry

~100ms

Current hardware registrations for a participant — GPU models, status, timestamps.

Hardware snapshots

~120ms

Per-epoch hardware history — scope by epoch for fast results.

Epoch performance

~150ms

Per-epoch inference and rewards counters by participant, with optional epoch range filter.

Full endpoint reference with parameters and examples: API documentation →

Fast, reliable RPCfor Gonka apps.