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, which stores an ID, name, description, media URL, and a `
This Sui package, `probably_nothing__wif_tie`, primarily manages `Nft` objects, which represent non-fungible tokens with attributes like `group_id`, `type`, `name`, `description`, `media_url`, and a `VecMap` of `attributes`. It also uses a `Manager` object to hold a `Display` object for `Nft`s, a `TransferPolicyCap` for `Nft`s, a `Balance<SUI>`, and a vector of `reserved_nft_ids`. The public/entry functions `withdraw_balance`, `withdraw_reserved_nfts`, `withdraw_royalties`, `add_nft_metadata`, `mint_nft`, and `update_nft` all immediately abort, suggesting they are either placeholders or intended for a future, more complete implementation. The `create_nft_with_verification` function creates a new `Nft` object and sets its ID within a `Verification` object, while `update_nft_with_verification` modifies an existing `Nft`'s metadata (
This package defines an NFT collection management system. The primary object type it manages is Nft, which has fields for group_id, type, name, index, description, media_url, and attributes (a VecMap of strings). The Manager object holds the collection's display object, a TransferPolicyCap for Nft, a SUI balance, and a vector of reserved Nft IDs. The public/entry functions are largely unimplemented, as indicated by the "Abort" instruction at the beginning of each. However, based on their signatures, they would likely allow for withdrawing balances, reserved NFTs, and royalties, adding NFT metadata, minting new NFTs, and updating existing NFTs. The `create_nft_with_verification` function creates a new Nft object and sets its ID within a Verification object. The `update_nft_with_verification` function modifies an existing Nft's name, description, media URL, and attributes, but only if the provided ID matches the one stored in the Verification object. Notable patterns include the use of a Manager object to
This package defines an NFT object, `Nft`, with fields for group ID, type, name, index, description, media URL, and attributes. It also manages a `Manager` object, which holds a display object, a transfer policy capability for the Nft, a SUI balance, and a vector of reserved NFT IDs. The `init`, `withdraw_balance`, `withdraw_reserved_nfts`, `withdraw_royalties`, `add_nft_metadata`, `mint_nft`, and `update_nft` entry functions are all aborted, indicating they are either placeholders or intentionally disabled. The `create_nft_with_verification` function creates a new `Nft` object and sets its ID in a `Verification` object, while `update_nft_with_verification` modifies an existing `Nft`'s metadata (name, description, media URL, attributes) if the provided `Verification` object matches the NFT's ID. The package utilizes `kiosk` for managing NFTs and `transfer_policy` for defining transfer rules, and includes events for
This Sui package, `chad`, primarily manages `Nft` objects, which represent non-fungible tokens with attributes like `group_id`, `type`, `name`, `description`, `media_url`, and `attributes` (a `VecMap<String, String>`). It also defines a `Manager` object that holds a `Display` object for `Nft`s, a `TransferPolicyCap<Nft>`, a `Balance<SUI>`, and a vector of `reserved_nft_ids`. The public/entry functions are largely unimplemented, as indicated by the `Abort` instruction at the beginning of most functions. The `init` function also aborts immediately. The `version` and `package_version
True specific-lot profit from 37 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_collectorflippernft_traderRule-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": "0x0bbc6246a7ffa772df7877ddb499a19149c043b124fdee2e9f5ef432b2186d24",
"n_tx": 587,
"n_successful_tx": 583,
"n_distinct_epochs": 114,
"n_distinct_sponsors": 0,
"first_seen_cp": 35973253,
"last_seen_cp": 205282164,
"first_seen_ts_ms": 1717639762505,
"last_seen_ts_ms": 1761499451571,
"total_gas_spent_mist": 3389392928,
"n_self_sponsored_tx": 587,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 754,
"active_hours_top24": [
18,
17,
19,
22,
1,
23,
5,
3,
16,
0,
15,
14,
20,
4,
21,
2,
6,
13
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector",
"flipper",
"nft_trader"
],
"label_confidence": [
0.745,
0.68,
0.664
],
"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