all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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 package defines a minter for NFTs. It manages two primary object types: `Collection` and `Minter`. A `Collection` represents an NFT collection, while a `Minter` object controls the minting process for a specific collection. The public/entry functions allow the owner of a `Minter` object to manage its sale phases. `add_phase` adds a new sale phase, `remove_phase` removes an existing phase, and `update_phase` modifies an existing phase. These functions mutate the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs. It checks the current sale phase based on the `Clock` timestamp, verifies a Merkle proof if a root is provided for the phase, and ensures the user has not exceeded mint limits for the phase or overall. It then transfers the minting fee to the `Minter`'s owner and creates a new `Nft` object, which is transferred to the minter. Notable patterns include time-gating for sale phases,
This Sui package, `puffy_nft`, primarily manages `Nft` objects, which represent digital collectibles with a name, description, media URL, and dynamic attributes. The `init` function sets up the package by creating a `Publisher` object, a `Display` object for `Nft` metadata, and a `TransferPolicy<Nft>` with a kiosk lock rule and a 3% royalty rule. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` all delegate to a `launchpad` module for various NFT minting functionalities, suggesting an external minting mechanism. The `update_nft` function allows a `Manager` to modify an existing `Nft`'s name, description, media URL, and attributes within a Kiosk. The package utilizes dynamic fields for NFT attributes and implements royalty and kiosk lock rules via the `TransferPolicy`.
This package defines a KEEPSAKE NFT, which is the primary object type. The init function sets up the collection, creates and shares transfer policies (one for transfer allowlisting, one for P2P listings, and a generic one), and transfers the MintCap and Publisher objects to the deployer. Public functions allow creating a collection with display info and royalty strategies, minting KEEPSAKE NFTs individually or in batches (mint, mint_to, mint_many, mint_launchpad), and burning KEEPSAKE NFTs. The package utilizes transfer policies for enforcing rules like allowlists and P2P listings, and integrates with a royalty system. It also provides functions for borrowing and returning KEEPSAKE NFTs or their fields, likely for interaction with other DeFi protocols.
This package defines a single object type, BBHIPPO, which is a dummy struct used as a type parameter. The `init` function is the only public/entry point and is called once during package deployment. It creates a new fungible token (a memecoin named "Baby Hippo" with symbol "BBHIPPO") and its associated `CoinMetadata` and `TreasuryCap` objects. The `CoinMetadata` object is frozen, making it immutable, and the `TreasuryCap` object, which controls the minting and burning of the token, is transferred to the deployer of the package. This package primarily focuses on the initial setup of a new fungible token on the Sui blockchain.
This Sui package defines a KEEPSAKE NFT, which is the primary object type. The init function sets up the collection, creates and shares transfer policies (one enforcing an allowlist, another for P2P listings), and initializes a display object for the KEEPSAKE NFTs. Public functions allow creating a new KEEPSAKE collection with royalty settings, minting single or multiple KEEPSAKE NFTs to a specific address or a listing, and burning KEEPSAKE NFTs. The package utilizes several patterns including admin capabilities (MintCap, TransferPolicyCap), dynamic fields (Attributes), and royalty mechanisms (keepsake_royalties, royalty_strategy_bps).
True specific-lot profit from 82 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
2 self-dealing round-trips excluded from the headline (gross incl. wash: $84).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
flippernft_traderRule-based labels, conservative precision.
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": "0xc522ed80357254cf9c84dada874ebc7ee9c3fffc316308f7eaaad0002744481e",
"n_tx": 8121,
"n_successful_tx": 7983,
"n_distinct_epochs": 414,
"n_distinct_sponsors": 3,
"first_seen_cp": 1731093,
"last_seen_cp": 279458891,
"first_seen_ts_ms": 1683284564748,
"last_seen_ts_ms": 1779699224550,
"total_gas_spent_mist": 28783959576,
"n_self_sponsored_tx": 8118,
"n_sponsored_tx": 3,
"gas_price_p50": 750,
"gas_price_p95": 890.21893,
"active_hours_top24": [
23,
7,
16,
14,
22,
8,
6,
15,
13,
12,
17,
19,
21,
0,
18,
20,
11,
10,
1,
9,
2,
3,
5,
4
],
"primary_archetype": "flipper",
"labels": [
"flipper",
"nft_trader"
],
"label_confidence": [
0.95,
0.875
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail