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 manages KEEPSAKE NFTs, which have a UID, name, description, URL, and attributes. The `init` function creates and shares a Collection object, a Display object, and two TransferPolicy objects (one enforcing `transfer_allowlist` and another enforcing `p2p_list`), along with their corresponding TransferPolicyCaps. It also transfers a MintCap and Publisher object to the transaction sender. The `create` function adds DisplayInfo and RoyaltyDomain to the Collection and sets up a royalty strategy on a TransferPolicy. The `mint` function creates a new KEEPSAKE NFT, increments the MintCap's supply, and emits MintEvent and mint_event::Mint events. The `mint_to` and `mint_many` entry functions mint multiple KEEPSAKE NFTs and either transfer them to a specified address or return them as a vector, respectively. The `mint_launchpad` function mints multiple KEEPSAKE NFTs and adds them to a Listing object. The `burn` function deletes a KEEPSAKE NFT. The
This package, my_minter, facilitates the creation and management of NFT collections and their associated minting processes. It primarily manages two object types: Collection, representing an NFT collection, and Minter, which defines the parameters and phases for minting NFTs within a collection. The init function initializes the package, creates a Display object for Nft metadata, and grants a CreatorCapability to the deployer. Public functions allow the Minter's owner to add, remove, and update SalePhase objects, which define minting parameters like price, maximum sales, mints per user, start time, and an optional Merkle root for allowlisting. The mint function allows users to mint NFTs if they meet the criteria of the active SalePhase, including payment and Merkle proof verification if an allowlist is active. Minting updates the Minter's minted count and user-specific buy counts. Notable patterns include: 1. Owner-gating: `add_phase`, `remove_phase`, and `update_phase` functions are restricted to the Minter's
This package facilitates the creation and management of NFT collections and their associated minting processes. It defines `Collection` and `Minter` objects, where a `Minter` manages the minting logic for a specific `Collection`. The `init` function initializes the package by creating a `Publisher` object, a `Display` object for `Nft` metadata, and a `CreatorCapability` object, all transferred to the sender. Public entry functions allow the `Minter`'s owner to manage "sale phases" using `add_phase`, `remove_phase`, and `update_phase`. These functions modify the `phases` vector within a `Minter` object, which dictates minting rules like price, maximum sales, mints per user, and start time. The `mint` function allows users to mint NFTs from a `Minter` object, requiring a `Coin<SUI>` for payment and verifying against the active sale phase's rules, including an optional Merkle tree root for allowlist gating. Notable patterns include owner-gating for phase
This Sui package primarily manages `Nft` objects, which represent non-fungible tokens with fields for ID, name, description, media URL, and attributes. The `init` function sets up display metadata for `Nft` objects and creates a `TransferPolicy` for them, adding a `kiosk_lock_rule` and a `royalty_rule` (10% royalty) before transferring the `Publisher`, `Display`, and `TransferPolicyCap` to the sender and sharing the `TransferPolicy` object. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module to handle the creation and distribution of NFTs, with `mint_edition_nft` also interacting with a Kiosk. The `update_nft` function allows a `Manager` to modify an existing `Nft`'s name, description, media URL, and attributes within a Kiosk, after delegating part of the update to the `launchpad` module. This package utilizes dynamic fields for NFT attributes and implements royalty
This package defines a system for managing and minting NFTs within a collection. It primarily manages two object types: `Collection` and `Minter`. A `Collection` represents an NFT collection, storing its name, description, and owner. A `Minter` object is associated with a `Collection` and handles the minting process, including tracking minted NFTs, managing sale phases, and user-specific purchase limits. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT sale, which modify the `phases` vector within the `Minter` object. The `mint` function allows users to purchase NFTs, updating the `minted` count in the `Minter` and the `user_buys` and `sale_phase_buys` tables. The `init` function initializes the package, creating a `CreatorCapability` for the deployer and setting up display metadata for NFTs. Notable patterns include: owner-gating for phase management functions, time-gating
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
nft_whaleflipperRule-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": "0xb4b02ff98a4bb82e4f226bb097800223fec953cfe367f91adffa39478119ea85",
"n_tx": 7022,
"n_successful_tx": 7011,
"n_distinct_epochs": 217,
"n_distinct_sponsors": 0,
"first_seen_cp": 1607807,
"last_seen_cp": 275682124,
"first_seen_ts_ms": 1683157543089,
"last_seen_ts_ms": 1778807533376,
"total_gas_spent_mist": 297844815084,
"n_self_sponsored_tx": 7022,
"n_sponsored_tx": 0,
"gas_price_p50": 815.04675,
"gas_price_p95": 950,
"active_hours_top24": [
4,
3,
17,
7,
16,
9,
8,
6,
2,
14,
13,
5,
18,
1,
10,
15,
22,
12,
11,
19,
20,
0,
23,
21
],
"primary_archetype": "flipper",
"labels": [
"nft_whale",
"flipper"
],
"label_confidence": [
0.36786515,
0.95
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail