Blockchain Genesis 2.0 testnetRunning testnet with a test import – not a production service, not audited, not approved by any regulator. A technical record, not a securities register.
Genesis Explorer
Transaction detail
—block —signatures on the latest block protocol finality —blocks verified last audit anchor— observer in sync

Contract register.

Every contract the network runs, where its code comes from and the hash of the code actually deployed. Anyone can recompute a code hash with eth_getCode and keccak256.

Code versions and who may change them

CodeVersion in useWho may change itAuthority

History of changes

Time (UTC)ChangeBlock · transaction

Role keys

Externally owned accounts that hold a role in the control plane. On the testnet they are derived from one seed held by the operator; in production each role key lives in the custody of the respective entity (HSM or multisig). The addresses are stable and every action they take is on chain.

RoleAddressPurpose

Check a code hash

  1. Fetch the deployed bytecode: eth_getCode(address, "latest") at https://rpc.blockgns.com.
  2. Hash it: keccak256(bytecode). It must equal the value in the table.
  3. For published sources (T-REX, ONCHAINID) compile the stated version with the same compiler settings and compare the runtime bytecode; proxies carry the proxy code, their logic sits at the implementation address.

Source provenance

Reconnecting to the network…