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, `keepsake_nft`, primarily manages `KEEPSAKE` objects, which are NFTs with a name, description, URL, and custom attributes. The `init` function initializes the NFT collection, creates and shares `Collection<KEEPSAKE>`, `TransferPolicy<KEEPSAKE>` objects, and transfers `MintCap<KEEPSAKE>`, `TransferPolicyCap<KEEPSAKE>`, and a `Publisher` object to the deployer. The `create` function adds display information and royalty strategies to the collection, enforcing transfer policies for royalties and P2P listings. NFTs can be minted individually (`mint`), to a specific address (`mint_to`), or in batches (`mint_many`), and can also be minted directly into a `Listing` object for launchpads (`mint_launchpad`). The package supports borrowing and returning NFTs or their fields via `BorrowRequest` objects, and `burn` allows for the deletion of `KEEPSAKE` NFTs. Notable patterns include the use of `MintCap` for controlled minting,
This package primarily manages KEEPSAKE objects, which are NFTs with a UID, name, description, URL, and attributes. The `init` function initializes the collection, creates a Publisher object, and sets up three TransferPolicies: one for general transfers with an allowlist, another for p2p listings, and a third for royalties, transferring their capabilities to the deployer and sharing the policies. The `create` function adds display and royalty domains to the collection and configures a royalty strategy for transfers. The `mint` function creates a new KEEPSAKE NFT, increments the supply in the MintCap, emits a MintEvent, and returns the NFT. There are also entry functions `mint_to` and `
This Sui package, `keepsake_nft`, primarily manages `KEEPSAKE` objects, which are NFTs with a name, description, URL, and attributes. The `init` function sets up the collection, creates a `MintCap` for minting, and establishes multiple `TransferPolicy` objects, including one for enforcing transfer allowlists and another for P2P listings, transferring the capabilities to the sender. Public functions allow for creating a collection with display info and royalty strategies, minting single or multiple `KEEPSAKE` NFTs, minting NFTs directly into a `Listing` object (launchpad), and burning `KEEPSAKE` NFTs. The package utilizes `MintCap` for controlled minting, `TransferPolicy` for managing transfers with specific rules (allowlist, P2P), and includes royalty mechanisms.
This package manages KEEPSAKE NFTs, which have a UID, name, description, URL, and attributes. The `init` function initializes the collection, creates and shares transfer policies (one enforcing an allowlist, another enforcing p2p_list, and a generic one), and sets up display information for the NFTs. Public functions allow for creating a new collection with royalty settings, borrowing and returning NFTs or their fields, and minting single or multiple KEEPSAKE NFTs. Minting functions include `mint`, `mint_to` (to a specific address), `mint_many` (returns a vector of NFTs), and `mint_launchpad` (adds minted NFTs to a listing). The package also includes a `burn` function to delete KEEPSAKE NFTs. Notable patterns include the use of `MintCap` for controlled minting, `TransferPolicy` for managing transfers with allowlist and p2p_list enforcement, and royalty mechanisms.
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.
casualRule-based labels, conservative precision.
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": "0x4480af9511f81e1b9e52e71df6bd5141b0d3b33d328afb3ceef5f7634ec92850",
"n_tx": 28,
"n_successful_tx": 28,
"n_distinct_epochs": 2,
"n_distinct_sponsors": 0,
"first_seen_cp": 1602147,
"last_seen_cp": 9660431,
"first_seen_ts_ms": 1683151727447,
"last_seen_ts_ms": 1691353735334,
"total_gas_spent_mist": 5933832776,
"n_self_sponsored_tx": 28,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
0,
1,
22,
23,
20,
14
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).