TOTAL SUPPLY
VIRENIX / ON-CHAIN DATA
VIRX overview
Examine supply, the founder lock, and the vesting schedule directly on-chain.
DATA PROVIDER
EVENT HISTORY SOURCE (OPTIONAL)
Not queried yet
Historical event logs are not always accessible or complete. Pocket Network may return archive errors for older blocks; a result from one source is not proof of the full history. FastNode does not support a direct browser connection and cannot be used without a secure server-side proxy. The two sources are compared only if both can actually be reached. If source access or evidence is insufficient, the history is marked incomplete or unavailable. VIRX / lock contract addresses, event types, and block ranges are sent to event-history sources; wallet addresses are not sent, and address filtering takes place on this page. Balance and allowance queries use the selected official BSC endpoints.
Latest block reading · finality not guaranteed
CURRENT LOCK BALANCE
—
VIRXRecorded founder lockCURRENTLY RELEASABLE
—
VIRXRelease amount at the referenced blockVESTING SCHEDULE
Observed state and overall 5-year target
—
FOUNDER LOCK
Current contract
CURRENT CONTRACT UNLOCK—Schedule will be read from chain.
- Released to date
- —
- Schedule duration
- —
- Current recipient / owner
- —
- Lock code exactly matches the archive
- —
Overall 5-year target
An additional lock is being developed and tested locally; it has not been implemented on-chain. This panel does not indicate that the five-year extension has been implemented or present the target date as a date read from the chain.
SOURCE & SCOPE
What data are you viewing?
CURRENT FOUNDER LOCK0x34DdDe27A1f9B95Ab66396b7d02eCCBc19C5E484 ↗
- Network, recorded lock address, and lock-code checks
- Amounts from the same block, revalidated using the block hash
- JSON report including submitted queries, block number, and hash
Data are responses from the single selected RPC provider. This is not an independent security audit.
Event history —
History has not been read. If no source is selected, history-dependent results remain unavailable.
The cache stores only public VIRX and lock events (no separately saved wallet addresses or keys) and is revalidated on each read. If reading is canceled or a source blocks access, completed ranges are retained; "Resume" continues where it stopped.
LOCK EVENT HISTORY
Founder lock events
Select an event-history source and choose "Read lock history" to fetch events. If no source is selected, the lock view relies only on owner(), start, and released values read from the official endpoint.
| Block / time | Event | Details | Transaction |
|---|---|---|---|
| Not read. | |||
This list shows only lock events that occurred on-chain; it does not establish that the overall 5-year target was implemented.
NO WALLET CONNECTION
Inspect an address's balance
This version reads BNB and VIRX balances. Other tokens are not included.
BNB BALANCE
VIRX BALANCE
A zero balance does not eliminate risks from spending allowances granted by this address.
VIRX SPENDING ALLOWANCE
Can this address spend VIRX?
Inspect the VIRX allowance a wallet has granted to a specific spender.
- Approved amount
- Spendable from current balance
- Code at spender address
The presence of code at an address does not mean it is safe; the absence of code does not mean it is harmless. This indicator is not an audit finding.
Scope of this check
Only the entered wallet–spender pair and VIRX are checked. This does not discover every approval; the result is not an overall "safe" verdict for the wallet.