$SNIFF
The curve completed 21s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
findingIt left the curve 21s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 18:54 UTC |
| Creator | 5HuFJ7n4KqaNWe9HYvXceJkDBtZD9H9uu3TZWGJD7heb |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 34 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Incomplete. We read the bonding curve account 1.8 days ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-29 19:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3hmg99yzMVaHxkbLTzDi13… slot 451,728,176
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 18:54:18 UTC Slot 451,728,176, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-29 18:54:40 UTC +21s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 18:54:45 UTC +26s
7.263e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 5 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | No other launch we hold a picture for used this one. |
| This ticker | On 7 launches from 5 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 14:24 UTC, just now |
What this launch claimed to be
| Name | Butt Sniffer |
| Description | We don't follow charts. We follow scents |
| Metadata held | sha256 d724f476773dbbea0e8eacd05e2f6c1be3573acaf72935371005af8e3a9d7767 · 340 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 18:54 UTC. |
| Picture held | sha256 c5043286aaa4d87087d1bc85d73769bbf12919854fcb6924776dacd935367dab · 217,603 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 18:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.