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, primarily managing `Minter` and `Nft` objects. The `init` function sets up display metadata for `Nft` and transfers a `CreatorCapability` to the deployer. Public functions allow the `Minter`'s owner to add, remove, and update `SalePhase` configurations within a `Minter` object, which define pricing, maximum sales, mints per user, and start times. The `mint` function allows users to mint NFTs by paying a fee, with checks for sale phase validity, user-specific mint limits, and overall supply limits. It also includes Merkle tree verification for allowlist-gated phases. The `Minter` object tracks total minted NFTs, and per-user/per-phase mint counts using dynamic fields (Tables).
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects for the individual NFTs and `SalePhase` objects to configure different minting stages. The `init` function initializes the package, creating a `Display<Nft>` object for metadata and a `CreatorCapability` object, both transferred to the sender. This `CreatorCapability` likely grants special administrative privileges. Public/entry functions include `add_phase`, `remove_phase`, and `update_phase`, which allow the `Minter`'s owner to manage `SalePhase` configurations within a `Minter` object. These functions mutate the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter`. It checks various conditions, including the current sale phase, available supply, user-specific mint limits, and a Merkle tree proof if a root is specified for the phase. It mutates the `Minter` object by incrementing `
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": "0x48bb1604b572c4cbcf191da34fa9b2937d57b790b9150c1d679f93fbf8af4318",
"n_tx": 123,
"n_successful_tx": 120,
"n_distinct_epochs": 17,
"n_distinct_sponsors": 0,
"first_seen_cp": 67203567,
"last_seen_cp": 85981968,
"first_seen_ts_ms": 1728505762598,
"last_seen_ts_ms": 1733114550087,
"total_gas_spent_mist": 384334624,
"n_self_sponsored_tx": 123,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
2,
18,
21,
19,
15,
1,
16,
0,
22,
20,
3,
4,
13,
23,
17,
5,
11,
7,
8,
9
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).