Every harvest the engine has executed — what reached the vault, how much owners have collected, and how the cadence has actually held up against its one-hour floor.
Paste any address that holds Veggies or has ever claimed. Everything below is read from this snapshot — nothing is sent anywhere, and no wallet connection is asked for.
| Asset | Amount | USD |
|---|
| Asset | Amount | USD |
|---|
The harvest captures about of $VEGGIES trading volume. This wallet’s cut is set by how many Veggies it has planted and at what tier. Slide the volume to see what that pays.
| Scenario | Daily volume | Whole collection / day | This wallet / day | / month |
|---|
| Token | Status | Tier | Pending USD |
|---|
One bar per harvest execution, oldest on the left. Measured from ERC-20 transfers into the harvest vault and priced at today's oracle rates. The scale is linear, which is why the opening days dwarf the rest — that is the finding, not a rendering artifact.
The contract enforces a minimum of one hour between harvests. Most gaps sit just above that line; the tall bars are stalls where the harvest simply did not run.
An owner plants a Veggie by burning 25,000 $VEGGIES. Counted in the interval it happened, on the same x-axis as the charts above — hover any of the three to read all of them.
Everything the vault has ever received, running total.
| # | Time (UTC) | Gap (h) | Routed USD | Assets | Activations | Claims |
|---|
Accrued and claimable, but not yet collected. Verified two independent ways: as vault token balances, and as the sum of pendingHarvest across all 4,444 token IDs.
| Asset | Routed in | Claimed | Unclaimed | Unclaimed USD | Share |
|---|