Its own first blocks
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-11-18 02:51 UTC |
| Creator | EPPNiPWDtyjeBCofLjdkh3ZQF8ty2MkK3CMsxVAuuotN |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 13 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: 13 within the first 30s, 13 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 4.9 h ago and it was finished. Checked 2026-11-18 03:08 UTC. |
| Creator sold | not while we watched |
| Recorded from | 261rTsJ5vZ8ZCucVK2PcL5… slot 470,774,116
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-18 02:51:07 UTC Slot 470,774,116, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-18 02:51:07 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-18 02:51:07 UTC +0s
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 | 13 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.
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Temple of :3 |
| Description | simply :3 everywhere. The :3 kitten hangs in a gold frame above the temple door, and the line goes around the block. Temple of :3, $TEMPLE3. Join the line; the address is on the sign at the end. |
| Metadata held | sha256 857b616c8863743d87a632a8633d38441d1d5fd2a63dce04a526088cf24d67f9 · 472 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. |
| Picture held | sha256 f56cd21cf3994f4edccb548d2df3539832f869d8011ffd0fa2feaea26babde2c · 1,379,131 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-18 02:51 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.