All received program notifications counted while connected; repeated deliveries can count again.
Explore / live monitoring
Watch the chain.
As activity arrives.
Continuous monitoring of finalized Pump-program logs on Solana mainnet.
Checking connection…Waiting for current status
Unique transaction signatures with a successful Pump Create instruction. Launch candidates, not verified project identities.
Source reports an execution error. These are excluded from launch candidates.
Live activity over 24 hours
Notifications received per hour. Empty periods do not establish an absence of chain activity.
What is running
A persistent live connection receives finalized Pump-program logs. Every received notification is counted. Successful Create instruction logs are stored privately with a source hash.
This monitors one program. Source outages create gaps. Recovery queues attempt to retrieve missing signatures and transaction records within the available request allowance. Counts are notifications, not complete transaction records or risk scores.
Launch decoding and supported transaction transfers are connected below. Metadata capture is active for supported public HTTPS and IPFS references. Risk classification, social-account verification, predictions and the production globe remain unavailable.
Coverage and development status →Recent live activity
| Minute | Notifications | Create notifications |
|---|---|---|
| Waiting for live history. | ||
Evidence processing
Checking transaction queue…
Pending records are incomplete work, not clean results. Recovered signature lists still require transaction retrieval.
1. Coin CA — launch funding
Paste the meme coin's Solana mint address (CA). Start with a retained SOL transfer from its launch transaction, then trace backward toward earlier funding or forward toward later movement. Token transfers are listed separately below.
Loading recent launches…
Launch-transaction transfers are starting points, not proof of the original funding source. TFA can trace only supported retained records; missing history remains unknown. Token-account transfers do not identify their wallet owners.
2. Wallet address — incoming and outgoing transfers
Paste a wallet address to inspect its retained account transfers. Choose a transfer and trace backward to earlier funding or forward to later destinations.
Enter a wallet address to begin.
This searches transfers directly involving the supplied account. It does not automatically include associated token accounts, verify the account type or establish who owns it. An empty result means no matching retained evidence.
Connection history
Interruptions remain visible. Automatic reconnection resumes activity. Recovery status and pending transaction work are shown below.
Public on-chain launch records and supported account transfers are shown here. Private watchlists and unreviewed findings remain private. Connection status refreshes every 10 seconds; use Recent launches to refresh the launch list.