Transaction by hash
~125msFull transaction details by hash — ideal for explorers and support.
Open access · Gonka mainnet
A community-operated gateway to the Gonka blockchain. No account. No API key. No rate limits. Full chain history, CosmWasm, and indexed data, backed by multiple independent nodes.
— req/s
Waiting for traffic…
No API key. No credit card. No rate limits. Just point at rpc.gonka.gg and go. Accounts and keys are deprecated.
Requests are load-balanced across 2 dedicated Feather RPC nodes, the Hyperfusion community node, and public fallbacks — with automatic health-checking and failover.
Archive nodes with pre-indexed transactions, addresses, hardware stats, and epoch metrics. Sub-50ms on complex queries that would take seconds on a raw node.
Chain RPC, REST API, CosmWasm, and indexed data behind one base URL. Change a single config line and your whole app is on gonka RPC.
Send transactions and read balances without chasing which public node happens to be up. Fewer "please try again" moments for your users.
Look up any hash or address across the full chain history, even for blocks from months ago.
Pull structured data for monitoring, reporting, or internal tooling instead of rebuilding archive infrastructure yourself.
One documented endpoint for Gonka instead of maintaining a list of fragile public URLs that go stale.
Real queries against the live index. No API key needed — just copy any command into a terminal and run it. Response times shown are typical for warm queries.
Full transaction details by hash — ideal for explorers and support.
Every transfer in a block height, ordered as they appeared on chain.
Full paginated history for any wallet — sent and received, newest first.
Slash records across the chain — filter by validator and height range.
Current hardware registrations for a participant — GPU models, status, timestamps.
Per-epoch hardware history — scope by epoch for fast results.
Per-epoch inference and rewards counters by participant, with optional epoch range filter.
Full endpoint reference with parameters and examples: API documentation →