Token Vesting Contract Explainer

WHAT IT DOES

Token Vesting Contract Explainer takes a vesting contract address or a transaction interacting with one, and provides a complete, plain‑language breakdown of the vesting schedule. It reads the contract’s state via public view functions—beneficiary, token, startTime, endTime, cliffDuration, vestingDuration, totalAmount, claimedAmount, vestedAmount, releasableAmount, and revoked status. It fetches the current block timestamp and computes the vesting progress percentage, whether the cliff has passed, and whether the schedule is fully vested. It also retrieves the token’s symbol and decimals for human‑readable amounts. Historical vesting events (TokensReleased, VestingCreated, VestingRevoked) are fetched using chunked, backoff‑aware log scanning to provide context on past claims and schedule changes. The output includes the beneficiary address, token name, total allocation, amount already claimed, currently releasable amount, start and end dates, cliff status, revocation status, a visual progress bar, and a plain‑language explanation of whether a claim transaction will succeed or fail.

HOW TO USE

Paste a vesting contract address or a transaction hash that interacts with a vesting contract into the input field, select the network, and click "Explain vesting". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the contract’s state. It attempts multiple common vesting function signatures to maximize compatibility with different vesting implementations (e.g., TokenVesting, VestingWallet, LinearVesting). It fetches the current block timestamp for schedule calculations. Historical events are fetched in chunks (500 blocks per request) with automatic backoff and halving on failure to avoid public RPC caps. The AI layer generates a plain‑English summary of the vesting schedule state, including whether a claim transaction would succeed. A visual progress bar shows how much of the vesting period has elapsed. You can click on the contract address or any address to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR VESTING EVENTS

Vesting events (TokensReleased, VestingCreated, VestingRevoked) provide crucial context—for example, confirming that tokens were previously claimed or that the schedule was revoked. However, public RPCs aggressively cap eth_getLogs block ranges; a full‑range request over 10,000 blocks will fail with a "block range too large" error. This tool automatically chunks log requests into 500‑block slices to stay within safe limits for all major RPC providers. If a chunk fails (due to timeout or provider‑specific caps), it halves that chunk and retries recursively—ensuring that even with aggressive caps, the tool reliably retrieves all relevant vesting events. The tool also caches the current block timestamp at the start of the scan to maintain consistency across all calculations and event fetches, preventing off‑by‑one errors when the chain advances during the scan. This is particularly important for vesting schedules where timing determines whether tokens are releasable.

WHAT IT CANNOT SEE

This tool cannot detect vesting schedules that depend on off‑chain state (e.g., vesting schedules that are managed by an off‑chain service or based on external data feeds). It cannot predict future vesting releases that might occur before the transaction is mined—the check reflects the current block, not the future. It cannot verify that the sender intended to claim or interact with the vesting schedule—the tool reads what is on‑chain, not the user's intent. It cannot detect vesting schedules in contracts that use non‑standard patterns (e.g., vesting logic that is not exposed via view functions, or custom vesting calculations that are not easily queryable). It cannot guarantee that a claim transaction will succeed even if tokens are releasable, as other conditions (e.g., paused state, balance, allowance) may also need to be met. It cannot detect if the vesting schedule has been revoked unless the contract exposes a public revoked() view function. It cannot detect token transfer restrictions that may prevent claiming (e.g., frozen tokens, or tokens that are not yet minted). It also cannot detect vesting schedules that are implemented as part of a larger token distribution contract without dedicated view functions.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche C‑chain, etc.) and relies on standard vesting function signatures (beneficiary, token, startTime, endTime, cliffDuration, vestingDuration, totalAmount, claimedAmount, vestedAmount, releasableAmount, revoked). It does not support custom vesting logic that does not expose these functions as public view methods. All explanations are AI‑generated from data the app reads on‑chain—the AI synthesizes the vesting state, schedule timeline, event history, and transaction context into plain English, but it does not have special access to private contract logic or off‑chain data. Always review what you are actually signing in your wallet before approving any transaction; a vesting explanation does not replace your own verification of the transaction details, including the target contract and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.