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 an `Nft` object type with fields for name, description, media URL, and attributes. The `init` function and several public functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) are effectively disabled, as they immediately abort. 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 `Nft`'s name, description, media URL, and attributes, but only if the provided `ID` matches the one stored in the `Verification` object and the `Nft` is held within a `Kiosk` owned by the caller. This package uses dynamic fields for NFT attributes and relies on an external `launchpad` module for verification.
This package defines an NFT collection for "Zodiac by Cryptofuckers NFT Club". The primary object managed is the `Nft` struct, which holds an ID, name, description, media URL, and dynamic attributes. The `init` function and most public functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) are unimplemented, causing a transaction abort if called. The `create_nft_with_verification` function creates a new `Nft` object with provided details and associates its ID with a `Verification` object from the `0launchpad` module. The `update_nft_with_verification` function allows modifying an existing `Nft`'s details (name, description, media URL, attributes) if the provided `Verification` object's associated NFT ID matches the target NFT, requiring a Kiosk and KioskOwnerCap for access. This suggests a pattern of gated access to NFT creation and updates via a separate verification mechanism.
This package defines an Nft object with fields for ID, name, description, media URL, and attributes (a VecMap of strings). The public entry functions mint_order, mint_nft, mint_edition_nft, and update_nft all immediately abort, indicating they are either placeholders or intentionally disabled. 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 modification of an Nft's name, description, media URL, and attributes, but only if the Nft's ID matches the ID stored in a provided Verification object, and the Nft is held within a Kiosk. This module utilizes dynamic fields for NFT attributes and relies on the launchpad module for verification.
This package primarily manages an "Nft" object type, which represents a non-fungible token with fields for name, description, media URL, and a map of attributes. The public functions "mint_order", "mint_nft", "mint_edition_nft", and "update_nft" all immediately abort, indicating they are either placeholders or intentionally disabled. The "create_nft_with_verification" function creates a new Nft object and sets its ID within a "Verification" object from the "launchpad" module. The "update_nft_with_verification" function allows modification of an existing Nft's details (name, description, media URL, attributes) if the provided Nft ID matches the one associated with the "Verification" object, requiring a Kiosk and KioskOwnerCap for access. A notable pattern is the use of an external "launchpad" module for verification, suggesting a gating mechanism for NFT creation and updates.
This Sui package manages `Nft` objects, which represent non-fungible tokens with attributes like `group_id`, `type`, `name`, `description`, `media_url`, and dynamic `attributes`. The core logic revolves around a `Manager` object that holds a `Display` object for `Nft` metadata, a `TransferPolicyCap` for `Nft` transfers, a `Balance<SUI>` for collected funds, and a list of `reserved_nft_ids`. Public functions allow for withdrawing collected SUI balance, withdrawing reserved NFTs from the manager, and withdrawing royalties from the associated `TransferPolicy`. NFTs can be minted, and their metadata updated, with royalty and kiosk lock rules enforced by the `TransferPolicy`. The package uses dynamic object fields to store reserved NFTs within the `Manager` object.
True specific-lot profit from 2 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).
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Tinted amber on the bubble map when they appear in the expanded graph.
flipperRule-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": "0xad6d9b67d0cea282a66f50bc97f551f57462ed96716498b59961e42eab2f07f6",
"n_tx": 2858,
"n_successful_tx": 2841,
"n_distinct_epochs": 375,
"n_distinct_sponsors": 3,
"first_seen_cp": 1803428,
"last_seen_cp": 282730386,
"first_seen_ts_ms": 1683359354983,
"last_seen_ts_ms": 1780507451476,
"total_gas_spent_mist": 12155183356,
"n_self_sponsored_tx": 2849,
"n_sponsored_tx": 9,
"gas_price_p50": 750,
"gas_price_p95": 752,
"active_hours_top24": [
7,
19,
8,
10,
9,
12,
18,
16,
15,
13,
17,
14,
11,
20,
6,
5,
21,
4,
23,
22,
3
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.5625
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail