timing leak heatmap · solana mainnet
Your wallet
keeps time.
Mainnet live · checking…
Status:
Ticker (placeholder, no token exists):
the working app
Read the clock on any address
One getSignaturesForAddress call returns up to 1,000 recent transactions with their block times. Optionally Clockleak decodes the newest ones to check which were actually signed by this address — incoming transfers and spam happen on other people's clocks.
Nothing is read until you press the button. Lookups are not stored — not on the server, not in this browser.
Show in
Activity
Week × hour heatmap
fewermorequietest 6 h
24-hour dial
How to blur your clock
how it works
Four readings of a public clock
- Read block times. Up to 2,000 signatures for the address, newest first, each with the block time the network recorded. One call per 1,000, through this site's read-only proxy.
- Check who signed (optional). Decode the newest 20–40 transactions to see whether the address actually signed them. Transfers sent to you, airdrops and spam show up in your history on someone else's clock; the "signed by it" layer keeps only your own actions.
- Draw the week. Bucket every timestamp into weekday × hour — in your browser's time zone or UTC — and find the quietest 6-hour stretch of the day.
- Guess like an observer. Most people sleep somewhere around 01:00–07:00 local time. If the quiet stretch is clear and the activity spans at least four different days, the offset between that stretch and 01:00 is a time-zone guess, shown with ±2 h uncertainty. If there is no quiet stretch, Clockleak says so instead of guessing.
privacy model
Who can see what
Kept private by Clockleak
- Your lookup: the address is not stored, logged or placed in the URL. The server relays allowlisted read-only RPC calls and keeps no query log.
- Your keys: nothing to sign, no wallet connection.
- The result: built and kept only in this tab; the CSV is generated locally.
Still visible
- Every block time is public forever — anyone can draw this heatmap for any address.
- Your IP and the address you query are seen by this site's host and the upstream RPC provider while relayed. Use a VPN or Tor if that matters.
- Off-chain timing — posts, messages, exchange logins — can be lined up against on-chain times and is often more precise.
Clockleak helps you reduce what your timing reveals. It does not make you anonymous.
Known limitations — please read
- A guess, not a location. The time-zone estimate assumes the quiet stretch is sleep. Night-shift workers, insomniacs, travellers, bots and shared wallets break that assumption. Heuristics from public data, not proof.
- Block time is approximate. It is the validator-reported time of the block, usually within seconds of when you clicked — good enough for hours, not for exact seconds.
- Not every signature is yours. "All signatures" includes transfers others sent to the address. The signer check covers only the newest 20–40 transactions; the share it finds is an estimate for the rest.
- Window only. At most 2,000 recent signatures; a very active wallet may cover only hours. The board shows the real span and number of distinct days, and refuses to guess on fewer than three days.
- Daylight-saving time is ignored in the guess (UTC offsets only). "Your time" uses your browser's own time zone rules.
- Experimental and unaudited. Reads go through a public RPC by default and can be rate-limited; failures are reported, never filled in.