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, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for a collection, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object. This function mutates the `Minter` object by updating `minted`, `user_buys`, and `sale_phase_buys` fields, and creates a new `Nft` object. Notable patterns include: - Owner gating: `add_phase`, `remove_phase`, and `update_phase` functions are restricted to the `Minter`'s owner. - Time-gating: The `mint` function checks the current timestamp against the `start_time` of the active sale phase. - Merkle tree verification: The `mint` function includes a `verify` call, suggesting a Mer
This package defines a dummy `AF_LP` object. Its single public function, `init`, is an entry point that creates a new LP coin using the `amm_interface` module, passing the `AF_LP` object and a constant value of 7 as arguments. The `init` function mutates the transaction context by creating this new LP coin. There are no other notable patterns like signature gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this module.
This Sui package defines a custom coin named "BOB". The primary object types it manages are CoinMetadata<BOB> and TreasuryCap<BOB>. The package has a single public/entry function, init, which is called once upon package deployment. This init function creates the "BOB" currency, mints an initial supply of 10,000,000,000,000,000 BOB tokens, and transfers them to the sender of the transaction. It then shares the CoinMetadata<BOB> object publicly and transfers the TreasuryCap<BOB> to a hardcoded zero address (0x0). A notable pattern is the use of a hardcoded image URL for the coin metadata.
This Sui package, `my_minter`, facilitates the creation and management of NFT collections. It defines `Minter` objects, which represent an NFT collection and hold details like name, description, supply, and a vector of `SalePhase` objects. `SalePhase` objects define different minting stages with specific prices, maximum sales, mints per user, start times, and optional Merkle roots for allowlisting. The `init` function sets up display metadata for `Nft` objects and creates a `CreatorCapability` for the deployer. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for a collection, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a collection, checking against the current active sale phase, verifying Merkle proofs if required, and updating the `minted` count, `user_buys` and `sale_phase_buys` tables within the `Minter` object
This package defines a system for managing NFT collections and their minting process. The primary object types are `Collection` (representing an NFT collection), `Minter` (managing the minting logic for a collection), and `Nft` (the individual NFTs). The `init` function initializes the module by creating a `CreatorCapability` object and transferring it to the sender, along with a `Publisher` and a `Display<Nft>` object. The `add_phase`, `remove_phase`, and `update_phase` public entry functions allow the owner of a `Minter` object to manage the different sale phases for an NFT collection, including setting prices, maximum sales, mints per user, and start times. The `mint` public entry function allows users to mint NFTs from a collection by paying the specified price in SUI, with checks for sale phase availability, user-specific mint limits, and overall supply limits. It also includes a Merkle tree verification logic for allowlist gating. Notable patterns include the use of `CreatorCapability` for administrative actions, `
True specific-lot profit from 1 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).
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_collectorRule-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": "0x738109e3812a429e188b261a3b6f168a01d3e90458ab517ddc0c862cb4fa5486",
"n_tx": 610,
"n_successful_tx": 609,
"n_distinct_epochs": 112,
"n_distinct_sponsors": 1,
"first_seen_cp": 97372430,
"last_seen_cp": 273118007,
"first_seen_ts_ms": 1735875254037,
"last_seen_ts_ms": 1778170136763,
"total_gas_spent_mist": 7428154908,
"n_self_sponsored_tx": 609,
"n_sponsored_tx": 1,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
18,
19,
3,
21,
20,
4,
13,
2,
23,
0,
14,
15,
16,
22,
1,
17,
5,
6,
12,
8,
7
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector"
],
"label_confidence": [
0.74
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).
area + brightness = call volume; hover for detail