UnyKorn Chain · Beta network

Network explorer

UnyKorn runs two chains: UnyKorn Chain Beta, written in Rust on the Polkadot SDK (blocks every six seconds, finalized by GRANDPA), and the EVM record chain (Besu QBFT, chain ID 37332). Their validators run in three regions across two providers (Oracle Cloud Ashburn, AWS Virginia, AWS Ireland), all operated by UnyKorn today. Every figure below is read from the networks and refreshes on its own; anything that cannot be read live says so.

Verify a record on the chain Verify a real payment See the Base checkpoints

Latest block–

Finalized block–

Block time–average of the latest blocks

UNY validators–Aura block production + GRANDPA finality

EVM validators–Besu QBFT, record chain 37332

Connected peers–as seen by the public RPC node

Runtime–

Latest blocks

Block	Hash	Produced	Validator	Extrinsics	Status
Reading the network…

UNY authorities

blocks in the latest window

Authority	Account	Node	Pairing	Blocks produced	Last block

Aura authorities and their session accounts are read live from the chain. Each account is matched to its node by account, and each match was checked on 25 October 2026 two ways: the node's own key store holds the same Aura and GRANDPA public keys, and the chain's session record for that account returns the same pair. Oracle nodes 1 to 4 are four validator processes on one Oracle Cloud host; each AWS node is its own instance. An account the registry cannot match is shown as unverified, never guessed.

Nodes

grouped by region

Node	Provider · region	EVM role	EVM address	UNY role	UNY account	Status
Reading the networks…

Three regions: Oracle Cloud (Ashburn), AWS Virginia (us-east-1) and AWS Ireland (eu-west-1), all operated by UnyKorn today. Roles come from the live validator sets where the chain can be read from the edge; "documented" means the figure is from the operations runbook, not a live read. A node is marked proposing only when one of the latest blocks carries its signature; followers have no public telemetry and show as unknown. The next milestone admits independent operators under an on-chain council.

Record batches on UnyKorn Chain

every 15 minutes

Each batch is a Merkle root over receipts, agent identity cards and internal records. Only fingerprints are written, never message text, names, wallet addresses or amounts.

Stream	Batch	Records	Block	Extrinsic	Written

Record chain and daily checkpoints on Base

…

Our EVM record chain (chain ID 37332) carries the same batches, and once a day a fingerprint of its latest block is written to Base, a public network UnyKorn does not run. Rewriting history would break that public link.

Record chain block: –
Consensus: –
Anchor registry: –

Record chain block	Base transaction	Base block	Written