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 a minter for NFTs. It primarily manages `Minter` objects, which represent an NFT collection's minting configuration, and `Nft` objects, which are the actual NFTs. The `init` function initializes a `Display<Nft>` object, which is used for displaying NFT metadata, and transfers it and a `Publisher` object to the transaction sender. Public/entry functions include `add_phase`, `remove_phase`, and `update_phase`, which allow the `Minter`'s owner to manage `SalePhase` objects within the `Minter`. These functions mutate the `phases` vector within the `Minter` object. The `mint` entry function allows users to mint NFTs. It checks the current time against sale phases, verifies a provided Merkle proof (if a root is set for the phase), and manages the number of mints per user and total sales per phase. It mutates the `minted` count, `user_buys` table, and `sale_phase_buys`
This Sui package defines a minter for NFTs. It manages three primary object types: `Collection` (representing an NFT collection), `Minter` (the core object managing the minting process), and `Nft` (the individual NFT object). The `Minter` object contains a vector of `SalePhase` structs, each defining a distinct sale period with its own price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlist gating. The `mint` entry function allows users to mint NFTs, checking against the current active sale phase, enforcing price, supply limits, and per-user mint limits, and optionally verifying a Merkle proof for allowlist access. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage these sale phases, including adding new phases, removing existing ones, and modifying their parameters. The `Minter` also tracks `minted` NFTs, `supply`, and uses `Table`s to store
This package defines a Minter object for managing NFT collections. It allows the owner to create and manage sale phases for NFTs within a collection. Users can mint NFTs by paying a specified price, with checks for maximum sales per phase and per user, and optional Merkle tree verification for allowlists. The package also includes utility functions for string and vector manipulation, and Merkle proof verification.
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function initializes the package by creating a `Publisher` and a `Display<Nft>` object, transferring them to the sender. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT sale, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs, which involves checking sale phase conditions (time-gating, max sales, mints per user, and an optional Merkle root for allowlist gating), transferring SUI coins, updating `minted` and `user_buys` fields in the `Minter`, and creating a new `Nft` object. The `Minter` object uses `Table` for `user_buys` and `sale_phase_buys` to track minting statistics.
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections and their associated sale phases. It also defines `Nft` objects, which are the individual NFTs minted. The `init` function initializes the package by claiming a `Publisher` object and creating a `Display<Nft>` object, transferring both to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage the `SalePhase` objects within a `Minter`, which define pricing, sales limits, and start times for different minting stages. The `mint` entry function allows users to mint NFTs from a `Minter` object, handling payment and enforcing sale phase rules like time-gating and potentially allowlist verification (via `root` in `SalePhase` and the `verify` function). Notable patterns include: owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions; time-gating for
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
area + brightness = call volume; hover for detail
{
"wallet": "0xeb1b12bb10cf9e12d6538e82e9c75f950270aaf81fd5cbb316e571755793642f",
"n_tx": 89,
"n_successful_tx": 88,
"n_distinct_epochs": 8,
"n_distinct_sponsors": 0,
"first_seen_cp": 2302407,
"last_seen_cp": 160295849,
"first_seen_ts_ms": 1683877858271,
"last_seen_ts_ms": 1750788041616,
"total_gas_spent_mist": 947161028,
"n_self_sponsored_tx": 89,
"n_sponsored_tx": 0,
"gas_price_p50": 931,
"gas_price_p95": 950,
"active_hours_top24": [
14,
15,
18,
16,
7,
12,
5,
4,
17,
13,
9,
19,
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).