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 an `Nft` object type with fields for ID, name, description, media URL, and attributes (a map of strings). The `init` function creates and configures a `Display` object for `Nft`s, a `TransferPolicy` for `Nft`s with a kiosk lock rule and a 50% royalty rule, and then transfers the `Publisher`, `Display`, and `TransferPolicyCap` objects to the transaction sender, while sharing the `TransferPolicy` object. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module for minting NFTs, with `mint_edition_nft` also taking a `Kiosk` and `KioskOwnerCap`. The `update_nft` function allows a `Manager` to modify the name, description, media URL, and attributes of an `Nft` held within a `Kiosk`.
This package primarily manages Nft objects, which represent non-fungible tokens with fields for name, description, media URL, and attributes. The init function sets up a Publisher object, a Display object for Nft metadata, and a TransferPolicy for Nft, adding a Kiosk lock rule and a 10% royalty rule to the policy. Public entry functions include mint_order, mint_nft, and mint_edition_nft, all of which delegate to a launchpad module to create new Nft objects and handle associated logic like payments and Kiosk interactions. The update_nft function allows a Manager to modify the name, description, media URL, and attributes of an existing Nft object, requiring a Kiosk and KioskOwnerCap if the NFT is in a Kiosk. Notable patterns include the use of a TransferPolicy with royalty and Kiosk lock rules, and the delegation of core minting logic to an external launchpad module.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0x9c623e9d9c2a9dc76fd9e9c354a44189121c8e7480bf15d1023052bcbca54e5d",
"n_tx": 62,
"n_successful_tx": 58,
"n_distinct_epochs": 8,
"n_distinct_sponsors": 0,
"first_seen_cp": 79990549,
"last_seen_cp": 192658338,
"first_seen_ts_ms": 1731651076537,
"last_seen_ts_ms": 1758533890109,
"total_gas_spent_mist": 324950952,
"n_self_sponsored_tx": 62,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
2,
10,
9,
11,
19,
14,
13,
12,
5,
3,
6,
4,
18,
17
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.