A record anyone can inspect.

Share a public link#

Open a mainnet schedule in the dashboard and select Public details or Copy public link. Share the link from the live website, not from localhost.

A link identifies both a workspace and a schedule ID. IDs start at 1 within each workspace, so an ID alone is not enough.

/vesting.html?workspace=WORKSPACE_ADDRESS&schedule=1

Open the public viewer ↗

What people can see#

Anyone with the address and ID can inspect the token, creator, beneficiary, original allocation, vesting dates, vested amount, claimed amount, claimable amount, and remaining allocation. Custom browser-local schedule names are not published onchain.

The viewer connects to the public mainnet RPC, checks the network and matching workspace code, and reads schedule state at a specific block. It displays that block and timestamp. Read again to update the snapshot.

Check the underlying records#

1. Use the workspace, token, creator, or beneficiary links in the viewer to open their explorer pages.
2. Follow the block link to identify the snapshot used for the amounts.
3. Check creation and claim transaction receipts in the explorer. The contract emits ScheduleCreated and Claimed events.

The contract read functions expose schedule terms and amounts independently of the app. An explorer may offer read-contract tools when the contract source/ABI has been verified there.

What “code verified” means here#

The app compares deployed runtime bytecode to its current VEYLOCK build. That is a compatibility check, not an independent audit, an endorsement of a token, or proof that its market value is reliable.

Onchain balances do not eliminate token issuer risks. See token compatibility and security status.