The Lester Labs explorer is a lightweight LitVM RPC client, not a full-history indexing service. It can look up an exact transaction hash or block number and display bounded recent samples for feeds, addresses, factory tokens, and transfers. A bounded sample can omit older activity and must not be used to prove that no other transaction, token, or holder exists. Confirmed transactions are chain records, but their long-term availability through this website or any particular public RPC is not guaranteed. When completeness matters, compare an independently selected archival data source and preserve exact hashes and receipts.
You do not need to connect a wallet to use read-only lookups. Exact lookups still depend on the configured RPC retaining and returning the requested data.
The search accepts Ethereum-format addresses, transaction hashes, and block numbers. Exact transaction and block routes request those objects directly. Address pages scan only the documented recent block window, so they do not show a full history.
Paste any LitVM wallet address into the search bar at lester-labs.com/explorer. Press Enter.
The page shows the current native balance and statistics derived from its recent scan. “First seen,” transaction counts, and counterparties refer only to that bounded sample. Contract-code presence is a current RPC observation, not verified source.
The transaction table shows matching transactions found in the newest 200-block scan, capped by the page logic. Older or otherwise unreturned activity is omitted. Open the exact hash for direct transaction fields.
The token table discovers Transfer logs in a bounded 10,000-block window and then reads balances for those discovered contracts. It can miss older holdings and is not a complete portfolio index.
Every LitVM transaction has a unique hash (0x...). On lester-labs.com/explorer, paste the hash into the search bar to open the transaction detail page.
The top of the transaction page shows Status (Success / Failed), the block number it was included in, and the gas used. A confirmed transaction shows the block number and a link to the block.
A method label is a best-effort decode against a known ABI. Verify the target, raw input, emitted logs, value, state changes, and receipt; a selector label alone does not prove what an unknown contract did.
Any decoded transfer section reflects logs returned and understood by the page. Compare raw receipt logs when completeness matters, because internal calls and nonstandard token behavior may not be represented.
Go to lester-labs.com/explorer/block/[number] or click a block number. The page requests that exact block and the transactions returned by the RPC.
Each block shows its number, timestamp, gas used, gas limit, transaction count, and the miner or validator address. Gas used vs limit tells you how full the block was.
The health view is a point-in-time RPC sample. It does not measure uptime, decentralization, historical liveness, finality, sequencer safety, or end-to-end network health.
Search by exact token address. Metadata and total supply are current contract reads; deployer/factory provenance is asserted only when a matching source-pinned factory event is found in the bounded scan.
The distribution view ranks inbound Transfer volume among logs in a bounded 10,000-block sample, capped by its log limit. It is not a current holder-balance reconstruction and cannot prove supply distribution.
The transfer list is a capped recent sample. It does not show every transfer and cannot independently audit a complete distribution. Use an archival index or source-pinned event range when completeness is required.
For any immutable-replacement or eligible legacy-recovery transaction, preserve the exact hash and verify its target, calldata, value, status, logs, and state change using more than one independently selected data source where practical. The Lester Labs explorer is a convenience interface to RPC data. It does not provide a completeness, archival-retention, contract-safety, or identity guarantee.