Block Explorer
The block explorer is the public window into Relix. It lets anyone inspect blocks, transactions, accounts, and smart contracts without running their own node, and it is an essential tool for both developers and users when debugging, verifying activity, or simply understanding what is happening on-chain.
For Relix Testnet, the official explorer is:
Relix Testnet Explorer:
https://testnet.relixchain.comNetwork: Relix Testnet
Chain ID:
4127
This page explains what the explorer offers and how to use it effectively.
1. What you can do with the explorer
The block explorer serves several core functions:
Inspect transactions
Check whether a transaction succeeded or failed
View gas used, fees paid, and the exact method called
See internal calls and emitted events (where supported)
Browse blocks
List recent blocks, their height, timestamp, and proposer
Inspect which transactions were included in each block
Track the growth and pace of the chain over time
View addresses and contracts
See balances and transaction history for any account
Distinguish between externally owned accounts (wallets) and contracts
Inspect contract code and ABI metadata once verified
Follow tokens
Track transfers for ERC-20 / ERC-721 / ERC-1155 style tokens
See holder counts and basic token information where available
For most users, the explorer is the first destination when they want to answer the question:
“What exactly happened in this transaction?”
2. Searching and navigation
The search bar on the explorer typically accepts multiple input types:
Transaction hash – to jump directly to a specific transaction
Address – to view all known activity for a wallet or contract
Block number or hash – to inspect the content of a particular block
Token contract – to see metadata and transfers for a specific token
A common workflow for developers:
Send a transaction from a dApp or script.
Copy the transaction hash from the wallet or console.
Paste it into
https://testnet.relixchain.comand open the transaction page.Confirm:
Status (success / fail)
Gas consumption
Logs and decoded events
This loop is especially useful during integration and debugging phases.
3. Transaction detail pages
A transaction detail view typically includes:
Basic metadata
From / To addresses
Value sent (in RLX and, where possible, in token units)
Nonce and gas limit
Execution data
Gas used, gas price / effective fee
Status (success, revert, pending if still in mempool)
Block number and timestamp
Logs and events
Raw logs emitted by contracts
Decoded events for known ABIs (if supported by the explorer)
For developers, the log and event section is critical. It allows you to:
Verify that specific events (e.g.
Transfer,Swap,Deposit) were emitted.Cross-check indexed parameters (addresses, IDs, amounts) against your expectations.
Debug why a particular UI did or did not update in response to a transaction.
4. Address and contract pages
When you search for an address, the explorer provides:
Overview
RLX balance
Type: EOA (wallet) or contract
Latest transactions in and out
Contract information
Contract creation transaction
Optionally, verified source code and ABI metadata
List of methods and events (for verified contracts)
Verifying contracts on the explorer (once supported) helps:
Users confirm they are interacting with the intended, audited code.
Frontends and tooling decode events and method calls more reliably.
Auditors and community members review logic directly from a trusted source.
As Relix matures, contract verification and metadata will become a standard part of publishing serious applications on the network.
5. Using the explorer in development workflows
The explorer is a key companion for daily development work on Relix:
After deployment
Confirm that your deployment transaction succeeded.
Note the contract address and bookmark the page.
Check that subsequent contract interactions behave as expected.
During debugging
Compare on-chain events and parameters against your local tests.
Identify where a transaction reverted and confirm the inputs used.
Monitor how gas usage changes as you update contract logic.
For monitoring
Watch activity on key contracts (DEX pools, vaults, system contracts).
Track growth of protocol usage via transaction counts and event volume.
Inspect large moves or unusual patterns when investigating incidents.
Integrating explorer links directly into your dApp (for example, “View on Relix Explorer” on transaction confirmation screens) gives users immediate transparency into what your application just did on-chain.
6. Testnet vs mainnet explorers
For now:
Testnet explorer:
https://testnet.relixchain.comNetwork: Relix Testnet (chain ID 4127)
As Relix advances toward mainnet, a separate explorer instance will be introduced for the production network. When that happens:
Testnet and mainnet explorers will be clearly separated.
Documentation and SDKs will reference the correct explorer URL per environment.
Developers should ensure their applications link users to the right explorer based on the connected chain.
7. Best practices when relying on the explorer
While the explorer is a convenient interface, it should be used alongside other tools:
For critical infrastructure, rely on your own nodes and monitoring in addition to the explorer UI.
Always confirm you are using the official Relix explorer URLs from:
https://relixchain.comhttps://github.com/relixchainOfficial Relix social channels
As the ecosystem grows, additional analytics dashboards and third-party explorers may appear, but the official Relix explorer will remain the canonical, neutral view of the chain’s state.
In short, the block explorer is where on-chain activity becomes human-readable. Whether you are a developer, validator, or end user, it is one of the most important tools for understanding and trusting what happens on Relix.
Last updated