Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-09-03 20:37 UTC |
| Creator | HDPFgtSJ3PpDbSsxxnVJeT4Z2iffru9q8J1L1n6TQ852 |
| Creator took | 79.3% of supply in the first block |
| Outside buyers | 0 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 0 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 5 min after launch |
| Curve on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | EANT74rfDKzxpJWb1s7Mrj… slot 444,064,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-03 20:37:19 UTC Slot 444,064,176, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No buyer, 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. |
| Curve completed | 2026-09-03 20:42:08 UTC +4m 50s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-03 21:15:09 UTC +37m 50s
1.316e-4 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 433 launches from 338 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
Who took the curve
One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
Pool
| Liquidity | 0.2 SOL |
| Read from chain | 2026-11-12 08:31 UTC, just now |
What this launch claimed to be
| Name | Beavercoin |
| Metadata held | sha256 9942a54987d9089ff7fdd8e867f769b6b71c3a734f6668386f92eb3a3936ca93 · 411 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-22 17:06 UTC. |
| Picture held | sha256 5d5ed527db755abbe7805611715f9b146d0690822f53475c1bc6c09cc51719aa · 372,607 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 10:32 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.