TOOLS / ADDRESS HISTORYConfirmed signatures

TRACE A PUBLIC ADDRESS

Wallet activity

Read a wallet, treasury or token account’s public transaction signatures. Page backward, inspect the movements and keep a small local record with an explicit retrieval time.

Choose an address.

Solana mainnet

No RPC requests run on page load.

Each page contains up to 20 signatures. An address appears when a transaction references it in account keys; this is not a holder index or complete payment ledger. Fee amounts and transfer contents require the transaction audit.

Local cache and backups

No browser-local save has been confirmed.

One address, five pages and 100 signatures maximum. Backups are capped at 100 KB. Imports are unverified saved observations, never live chain proof. Browser storage can be cleared by your browser; export a backup to keep a copy.

Signature timeline.

No observation

Public RPCs can prune older data, rate limit or return an empty page. Pagination does not establish full history coverage. Saved values are not automatically refreshed, finalized again or backed up to a cloud service.

RPC scope

VEYDUCT verifies the selected network’s genesis hash, then calls getSignaturesForAddress with confirmed commitment, a fixed limit of 20 and an optional before signature. There are no background reads or wallet permissions.

Official Solana RPC reference