all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This Sui package defines an NFT collection for "PEPE_ON_SUI_OG_COLLECTION". The primary object type it manages is `Nft`, which has fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init`, `mint_order`, `mint_nft`, `mint_edition_nft`, and `update_nft` functions are all unimplemented (they immediately abort), suggesting that core minting and updating logic is handled externally or is not yet defined. The `create_nft_with_verification` entry function creates a new `Nft` object and sets its ID within a `Verification` object, likely for a launchpad integration. The `update_nft_with_verification` entry function allows modification of an existing `Nft`'s name, description, media URL, and attributes, but only if the provided `ID` matches the NFT ID stored in the `Verification` object, and it requires a `Kiosk` and `KioskOwnerCap`
This Sui package defines a fungible token named PEPE. The `init` function creates the `CoinMetadata<PEPE>` and `TreasuryCap<PEPE>` objects. It mints an initial supply of 42,069,000,000,000,000 PEPE tokens and transfers them to the deployer. The `TreasuryCap<PEPE>` is then transferred to a hardcoded zero address, effectively burning it and preventing further minting. The `CoinMetadata<PEPE>` object, which contains details like the token's name, symbol, description, and an image URL, is shared publicly.
This package defines a dummy `AF_LP` object. Its `init` function, which is called once upon package publication, creates a new LP coin type by calling `amm_interface::create_lp_coin` with the `AF_LP` type, a constant value of 3, and the transaction context. This suggests the package primarily serves to register a new liquidity pool token type within an AMM system. The `AF_LP` struct itself contains only a boolean `dummy_field`, indicating it's likely a marker type rather than holding significant data. There are no other public or entry functions, nor any notable patterns like admin caps or time-gating.
This package defines a single dummy struct `AF_LP` which has the `drop` ability. The `init` function, which is likely a module initializer, calls `amm_interface::create_lp_coin` with an instance of `AF_LP`, a constant value of 4, and the transaction context. This suggests the module is registering `AF_LP` as a liquidity pool coin within an Automated Market Maker (AMM) system. The `AF_LP` struct itself has no functional fields, indicating it serves primarily as a type identifier for the AMM. There are no other public or entry functions, and no notable patterns like signature gating, time-gating, or admin caps are present in this IR.
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0x560979b2325d0c64574e46522e5a8a4e28a1867f4d3756e0f53e966a688ac6fe",
"n_tx": 261,
"n_successful_tx": 260,
"n_distinct_epochs": 82,
"n_distinct_sponsors": 0,
"first_seen_cp": 68303851,
"last_seen_cp": 230253760,
"first_seen_ts_ms": 1728774134662,
"last_seen_ts_ms": 1767375200466,
"total_gas_spent_mist": 917135376,
"n_self_sponsored_tx": 261,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
23,
4,
21,
17,
11,
5,
16,
0,
1,
22,
15,
3,
18,
12,
20,
2,
10,
19,
14,
9,
7,
13,
8,
6
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).