bounty.ai
The curve completed 12s 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 12s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 07:30 UTC |
| Creator | 58aKfkRJfQY8CzYvsYiu3qmYEBcoC4wmkaFjCai6ARxX |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 35 distinct wallets, not counting the creator, bought on the bonding curve: 4 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.6 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-30 07:32 UTC. |
| Creator sold | yes |
| Recorded from | 35NG3fVysD8U6i6sHgfEj5… slot 451,897,669
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 07:30:16 UTC Slot 451,897,669, 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-30 07:30:28 UTC +12s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 07:30:28 UTC +12s
1.201e-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 | 4 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 creator | 45 earlier launches, 2 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 other creator wallets, across 5 shared artifacts, each matched by hash. Together they sit in a linked group of 7 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 23:02 UTC, just now |
What this launch claimed to be
| Name | bounty.ai |
| Metadata held | sha256 56e453253d043033e1dc8a294ad03a1f2f138e40c11b715ace8a898daac9b070 · 300 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-10-01 07:31 UTC. |
| Picture held | sha256 feaf6e0219b6b7d51128dff512d023cb9ca6f8e10bd3339789f4f14dbe295ad5 · 1,209 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 07:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.