VEIL Scan / public trail
Reading the public ledger
Collecting the last 100 available signatures
Asking public RPC for signatures, then parsing transaction bodies. Public data only. No wallet. No signature.
VEIL Scan / public trail
This report uses only public Solana data. Nothing was signed. A transfer is evidence of interaction, not of a shared owner. How this is built · FAQ
Exposure index
High exposure
Higher means more of this address already lives in public ledgers, logs, and indexers.
From 47 public signatures, an observer can see counterparties, amounts, program usage, and timing. Transfer does not mean common ownership.
47 signatures are visible to anyone with an RPC node or explorer.
Solana transactions are broadcast, stored by validators, and served by public RPC. Signatures, timestamps, fees, account lists, and program calls remain readable indefinitely.
It paid fees on 46 of 47 scanned transactions.
The fee payer is account zero in the transaction. That usually means this wallet signed and submitted the transaction, which is stronger evidence of control than receiving funds.
3 other addresses appear in transfers or token balance changes.
A transfer is not proof that two addresses share an owner. It is proof they interacted on-chain. Repeat flows, change patterns, and shared funding sources are what analysts use next.
About 5.000 SOL in and 9.990 SOL out across this window.
Balance changes are computed from pre/post account balances. Token amounts are similarly public unless a program uses a confidentiality extension.
This address talked to Memo, Jupiter v6, Pump.fun.
Program ids are public. Swaps, NFT markets, lending, and bridges describe what the wallet does, not just that it exists. Reusing one address across apps links those behaviors together.
2 memos can be read without any special access.
Memos are the most common accidental leak: invoices, notes, referral codes, even names. They survive forever in the ledger.
05 / Transfer map
A line means value or a token account moved between these addresses. It does not mean they have the same owner.
03 / Applications
Reusing one wallet across apps publishes a combined profile: trading, minting, lending, and bridging become one public story.
Base ledger operations
Native SOL transfers, account creation, and rent.
Public plaintext
Arbitrary plaintext attached to a transaction. Fully public.
Trading and liquidity
Swap aggregator. Reveals trading routes and token pairs.
Trading and liquidity
Memecoin launches and trades. A strong behavioral fingerprint.
Proofs from the ledger
Each row is a public signature you can open in an explorer. VEIL Scan does not add off-chain identity.
| Finding | Label | When | Signature |
|---|---|---|---|
| Transaction history is public | Confirmed signature | Sep 21, 2026, 10:53 AM | veilDe…111111 |
| Transaction history is public | Confirmed signature | Sep 21, 2026, 6:53 AM | veilDe…111111 |
| Transaction history is public | Failed transaction still public | Sep 21, 2026, 3:53 AM | veilDe…111111 |
| This address initiated activity | Fee payer | Sep 21, 2026, 10:53 AM | veilDe…111111 |
| This address initiated activity | Fee payer | Sep 21, 2026, 6:53 AM | veilDe…111111 |
| This address initiated activity | Fee payer | Sep 21, 2026, 3:53 AM | veilDe…111111 |
| Counterparties are visible | sent to 8FgK2nQ1sH4dL7pR0vC6yU3bE9tA5wJ2mX1zS4oP8qHt 7.8000 SOL across 43 transfer(s) | Sep 14, 2026, 2:53 AM | veilDe…111111 |
| Counterparties are visible | received from 5qB9nM2wL8cT4yR1vH7dP6sA3uE0jF5gX2zN9cK8mLpW 5.0000 SOL across 1 transfer(s) | Sep 20, 2026, 6:53 PM | veilDe…111111 |
| Counterparties are visible | sent to 2VkL9cM4wQ7nT6yR1bH8dP3sA0uE5jF2gX4zN7cB9mLq 1.5000 SOL across 1 transfer(s) | Sep 20, 2026, 6:53 AM | veilDe…111111 |
| Amounts moved in public view | Balance change recorded | Sep 21, 2026, 10:53 AM | veilDe…111111 |
| Amounts moved in public view | Balance change recorded | Sep 21, 2026, 6:53 AM | veilDe…111111 |
| Recognized programs fingerprint behavior | Memo 2 instruction(s) | Sep 20, 2026, 6:53 AM | veilDe…111111 |
| Recognized programs fingerprint behavior | Jupiter v6 1 instruction(s) | Sep 21, 2026, 6:53 AM | veilDe…111111 |
| Recognized programs fingerprint behavior | Pump.fun 1 instruction(s) | Sep 21, 2026, 3:53 AM | veilDe…111111 |
| Plaintext memos are on-chain | Public memo invoice 1842 / alice@studio.example | Sep 21, 2026, 10:53 AM | veilDe…111111 |
| Plaintext memos are on-chain | Public memo payroll week 12 | Sep 20, 2026, 6:53 AM | veilDe…111111 |
| Failed transactions still leak intent | Failed signature | Sep 21, 2026, 3:53 AM | veilDe…111111 |
| Program logs include application-shaped data | Program log Program log: invoice 1842 / alice@studio.example | Unknown time | veilDe…111111 |
Privacy debugger
Instruction data, memos, and program logs are part of the public transaction. If your client put a user id in any of them, it is already on every indexer.
memo
The Memo program stores UTF-8 text on-chain. Anyone can read it from an explorer or RPC node.
invoice 1842 / alice@studio.example
Do not put user ids, invoices, emails, or application state in memos. Keep correlation data off-chain or commit to a hash.
veilDemo…11111111log
msg!() and program logs are replicated by RPC nodes and indexers. They are not private.
Program log: invoice 1842 / alice@studio.example
Log instruction names and error codes, never emails, URLs, user ids, or order references.
veilDemo…11111111instruction-data
Program JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4 received raw instruction bytes. If the client encoded application payloads here, they are visible to every indexer.
routeUsdcToSolCustomerId9941
Keep user identifiers and business payloads out of instruction data. Prefer commitments, encryption, or a shielded design.
veilDemo…11111111memo
The Memo program stores UTF-8 text on-chain. Anyone can read it from an explorer or RPC node.
payroll week 12
Do not put user ids, invoices, emails, or application state in memos. Keep correlation data off-chain or commit to a hash.
veilDemo…11111111Solana transactions are broadcast, stored by validators, and served by public RPC. Signatures, timestamps, fees, account lists, and program calls remain readable indefinitely.
Balance changes are computed from pre/post account balances. Token amounts are similarly public unless a program uses a confidentiality extension.
Program ids are public. Swaps, NFT markets, lending, and bridges describe what the wallet does, not just that it exists. Reusing one address across apps links those behaviors together.
Memos are the most common accidental leak: invoices, notes, referral codes, even names. They survive forever in the ledger.
A failed swap or mint still shows the program, the accounts, and often the attempted amount. Failure is not erasure.
Solana program logs are part of the transaction metadata that RPC nodes return. Anything a program prints is part of the public trail.