tappy
The curve completed 10s 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 10s after launch.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 20:28 UTC |
| Creator | GdhsAdTfDN9og7g2a7xF4Xubt61K65KMLZynHYUZi8o9 |
| Creator took | 1.9% of supply in the first block |
| Outside buyers | 134 distinct wallets, not counting the creator, bought on the bonding curve: 134 within the first 30s, 18 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.7 days ago and it was finished. Checked 2026-09-29 20:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 431qdkU5JvF1PBPBScaevF… slot 451,749,320
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 20:28:47 UTC Slot 451,749,320, which is the chain's own clock for this moment. |
| Creation block | 18 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 20:28:58 UTC +10s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 20:28:58 UTC +10s
4.109e-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 | 134 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 | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 4 launches from 4 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-01 13:25 UTC, just now |
What this launch claimed to be
| Name | tappy |
| Description | Launch your first token with Apple Pay, PayPal, or a card |
| Metadata held | sha256 ac7754d15a90f6c5aecfa520081e19382f04582d7b71375fcb127d1864b6a784 · 310 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 20:30 UTC. |
| Picture held | sha256 70c3bb9bc1b483b85d30df0cc46d32e6769cedd9a33d94ab7357c7726a3af617 · 26,949 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.