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 system for managing NFT collections and their minting processes. It primarily manages `Minter` objects, which represent an NFT collection and its associated minting configuration, and `Nft` objects, which are the individual NFTs. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the minting process, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs, which involves checking various conditions (time-gating, supply limits, Merkle proof verification if applicable) and then creating a new `Nft` object, updating the `minted` count in the `Minter`, and transferring the SUI payment to the `Minter` owner. Notable patterns include: owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions; time-gating for minting based on `start_time` in `SalePhase`; optional Merkle proof verification (`root`
This package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects, `SalePhase` objects for managing minting phases, and a `CreatorCapability` for administrative actions. Public functions allow the `Minter` owner to add, remove, and update `SalePhase` configurations, which include price, max sales, mints per user, start time, and an optional Merkle root for allowlist gating. The `mint` function allows users to mint NFTs from a `Minter` object, checking against the active sale phase's rules, including price, supply limits, per-user limits, and Merkle proof verification if an allowlist is enabled. The `mint` function mutates the `Minter` object by updating the `minted` count, `user_buys` (tracking user-specific mints), and `sale_phase_buys` (tracking phase-specific mints). It also transfers SUI from the user to the minter's owner
This package primarily manages `Nft` objects, which represent digital collectibles with a `UID`, `name`, `description`, `media_url`, and a `VecMap` of `attributes`. The `init` function initializes a `Publisher` object, a `Display` object for `Nft` metadata, and a `TransferPolicy` for `Nft`s, which includes a `kiosk_lock_rule` and a `royalty_rule` set to 100 basis points (1%). These objects are then transferred to the sender or shared. The `create_nft_with_verification` function creates a new `Nft` object and associates its ID with a `Verification` object from the `launchpad` module. The `update_nft_with_verification` function allows modifying an existing `Nft`'s metadata (name, description, media_url, attributes) if the provided `ID` matches the one stored in the `Verification` object, or if the `Nft` is managed within a `Kiosk` by its `KioskOwner
casualRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
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": "0xf6d9be71fc9eb161a4fcfc5afb091fdf01d0644f2240e3ce0f95a55597d9ce3a",
"n_tx": 39,
"n_successful_tx": 30,
"n_distinct_epochs": 14,
"n_distinct_sponsors": 0,
"first_seen_cp": 101670535,
"last_seen_cp": 189420931,
"first_seen_ts_ms": 1736914333007,
"last_seen_ts_ms": 1757747656577,
"total_gas_spent_mist": 190323356,
"n_self_sponsored_tx": 39,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
4,
9,
0,
2,
10,
20,
5,
7,
11,
8,
1
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. Asia / Oceania.