Check every figure yourself

What each figure proves

A signature written into a coin's metadata file is checked by nothing on chain. The figures above are different: each is an account balance, an account's contents or a landed transaction, and Solana itself is the record.

Vaults open on chain

Each vault is an account owned by the vault program. Its address commits to the vault's first hash-based public key, so nobody can swap the key behind an address. Open the program on Solscan to see the accounts it owns.

One-time keys spent

Every move out of a vault uses one hash-based key, once. The vault account counts them, and the program refuses a key that was used before. This number is the keys used in each vault's current key set plus one per rotation.

Key rotations

Before a key set runs out, the vault moves to a fresh one at the same address. The account records how many times that happened.

Who can change the program

Read from the program's own data account. If an upgrade authority exists, it is shown here as what the chain says it is: a single key, a multisig with its time lock, or nobody.

Sealed launches

A coin counts only when the vault program holds a launch record for it and pump.fun's fee split is locked with the vault's address receiving the creator share. The verifier repeats that check in your browser with any RPC.

What the vaults hold

The SOL and dev bag at each coin's vault address, read from chain. No wallet key controls that address. Only a hash-based signature checked by the program moves anything out.

Fees and the platform share

Each collection is one transaction that pays the creator's share to the vault address and 20% of creator fees to one platform wallet. Both amounts are read from the landed transaction.

$HASHLOCK burned

All of the platform share buys $HASHLOCK and burns it. A burn lowers the token's supply for good, and each one is a transaction you can open.