Bot or human?
Bots trade around the clock in even, dense rows. People leave a sleep-shaped gap. The heatmap shows which you're looking at in a glance.
24/7 = probably automated
FOLIO Nº 1 · SOLANA MAINNET
Every wallet keeps books.
We just rule the columns.
LedgerLine reads a wallet's public transaction signatures and enters them into a ledger: a heatmap of activity by day and hour, a journal of every entry, the failed ones in red ink, and the quiet gaps between.
Network day-book—
−60 min−30now
- Entries, last hour
- —
- Per second, avg.
- —
- Busiest minute
- —
Acct. 101
Open a wallet's books
Paste any Solana address. LedgerLine pages through its signatures (up to 5 × 1,000) and posts them to the ledger below.
try one →
Nothing posted yet.
Choose a sample account or paste an address to start a page.
Acct. 102
Method of account
- I.
Request the signatures
Your browser calls
getSignaturesForAddresson a public Solana RPC. Each call returns up to 1,000 signatures, newest first, with slot, block time, error status and any memo. - II.
Turn the page
To go further back it asks again with
beforeset to the oldest signature so far, waiting between calls, until it hits your depth or the node's history ends. - III.
Post by the clock
Each block time is converted to your local time (or UTC) and posted to a day × hour grid — or, for busy accounts, an hour × five-minute grid.
- IV.
Close the books
Totals are ruled off: entries, failures, active hours, busiest hour, longest quiet gap and the account's daily rhythm. Export it all as CSV if you want to keep the page.
Acct. 103
What the ledger is good for
Check your own privacy
Your activity pattern can hint at your timezone and routine. Look at your own wallet the way a stranger could.
quiet hours = night?
Find the failures
Failed transactions still cost fees. See how many of an account's entries failed and when they cluster.
red ink = err ≠ null
Spot a dormant wallet waking
Long quiet gaps followed by a burst of entries are worth noticing — for a treasury, a team wallet, or your own old address.
gap → burst
Read the memos
Entries that carry a memo are listed with their text, which often explains what a payment was for.
memo column
Keep a record
Export signatures with times and status as CSV for your own bookkeeping or to look up details later.
file it away
Acct. 104
Reading signatures like an accountant
A signature is a receipt number
Every Solana transaction is identified by its first signature — a 64-byte Ed25519 signature written in base58, usually 87–88 characters. It is unique, permanent and public, which makes it the perfect ledger reference: paste it into any explorer and you get the full transaction.
"For address" means "mentioned", not "sent"
getSignaturesForAddress returns transactions in which the address appears among the account keys — not just ones the wallet signed. Incoming transfers, airdrops someone else paid for, and programs that merely read the account all show up. A wallet that never signs anything can still have a busy ledger, so read heavy activity with that in mind.
What each entry carries
Alongside the signature you get the slot it landed in, a blockTime (Unix seconds, from validators' vote timestamps, so it can be a little off), the err field (null when the transaction succeeded), the confirmationStatus, and a memo if the transaction used the Memo program. LedgerLine posts all of these without fetching full transactions, which keeps it to a handful of requests.
Failed still means recorded
On Solana a transaction that fails after being processed is still included in a block and still pays its fees — the instructions simply don't take effect. That's why failures appear in the ledger in red ink. Trading bots often show many: they submit aggressively and let the chain reject trades whose price moved.
Why the history is short here
Validators don't keep the whole ledger. Full history lives in archival storage that RPC providers may or may not expose. The free public node LedgerLine uses keeps a rolling window of recent history — anywhere from several hours to a couple of days, and it shifts over time. When the node's history runs out, LedgerLine says so and shows the earliest entry it could reach. For deeper history you'd need an archival RPC.
Patterns worth knowing
Even rows across all 24 hours suggest automation. A daily dark band suggests a person asleep — and therefore a rough timezone. Bursts in one five-minute bucket often mean a batch job or a bot reacting to a launch. Treat all of it as a hint, never as proof of who owns an address.
Acct. 105
Queries from the auditors
Does LedgerLine see token transfers and amounts?
No — it reads signatures only, not full transactions, so it knows when something happened and whether it failed, not what moved. Click any signature to open it on an explorer for details.
Why does a busy wallet only cover an hour or two?
Depth is counted in entries, not days. At 5,000 entries a wallet doing thousands of transactions an hour only reaches back a short time. LedgerLine switches to an hour × five-minute grid for that case.
Why did the history stop after a day or two?
The public RPC node keeps a limited rolling window of history, often less than two days. When it has nothing older, LedgerLine marks the page "end of available history" and shows the earliest date reached.
Can I look up a program or token mint instead of a wallet?
Yes, any account address works. Very busy programs will fill 5,000 entries in seconds of chain time, so the grid will be narrow.
Is local time accurate?
Block times come from validator timestamps and are usually within a second or two. LedgerLine converts them with your browser's timezone; switch to UTC for a neutral clock.
What does "longest quiet gap" mean?
The longest stretch between two consecutive entries within the period loaded. It can't see gaps before the first entry LedgerLine reached.
Is anything stored?
No. There is no backend. Addresses go directly from your browser to the public RPC, and the CSV is generated in your browser.
Limits & honesty
- Source:
getSignaturesForAddressandgetRecentPerformanceSampleson the public RPC at solana-rpc.publicnode.com, called from your browser. - History window: that node keeps only a rolling window of recent history (we have seen it range from under a day to about two days). Older activity simply isn't returned.
- Depth cap: at most 5 pages × 1,000 signatures, with a pause between pages, to share the public node fairly.
- Mentions, not ownership: entries include any transaction that references the address, including spam and transfers sent by others.
- No amounts: LedgerLine doesn't decode transactions, so it can't show balances or profit and loss.