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 with fields for ID, name, description, media URL, and attributes (a VecMap of strings). It also defines a dummy `REBELZ00` object. The `init` function and most public/entry functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) immediately abort, suggesting they are either placeholders or intended for future implementation. The `create_nft_with_verification` function creates a new `Nft` object, populating its fields, and then calls an external `launchpad::set_verification_nft_id` function, associating the newly created NFT's ID with a `Verification` object. The `update_nft_with_verification` function allows modification of an existing `Nft`'s name, description, media URL, and attributes, but only if the provided `ID` matches the one stored in the `Verification` object, or if the `KioskOwnerCap` is present. This indicates a form of access control or verification gating
This package defines a single primary object type, `REBELZ`, which is a dummy struct used to represent a fungible token. The `init` function is an entry point that creates a new `REBELZ` currency, mints its initial supply, and transfers the `TreasuryCap` and `CoinMetadata` to the deployer's address. This effectively sets up the REBELZ token with a fixed supply and assigns administrative control (via `TreasuryCap`) to the deployer. The `init` function also sets the token's name, symbol, description, and an image URL. The package utilizes standard Sui framework modules for coin creation and transfer, and it does not exhibit any notable patterns like signature/allowlist gating, time-gating, dynamic fields, or vault/escrow mechanisms beyond the standard `TreasuryCap` for minting/burning.
This Sui package, `rebelz_adeniyi`, primarily manages an `Nft` object type, which includes fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). 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` entry function creates a new `Nft` object with provided metadata and associates its ID with a `Verification` object from a `launchpad` module. The `update_nft_with_verification` entry function allows modification of an existing `Nft`'s metadata (name, description, media URL, and attributes) if the provided `Nft` ID matches the one stored in the `Verification` object and the caller has the `KioskOwnerCap` for the `Kiosk` where the `Nft` is held. This package utilizes a verification pattern, likely for access control or
This package defines an `Nft` object with `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init`, `mint_order`, `mint_nft`, `mint_edition_nft`, and `update_nft` functions are all unimplemented, simply aborting. The `create_nft_with_verification` function creates a new `Nft` object and sets its ID within a `Verification` object from the `0launchpad` module. The `update_nft_with_verification` function allows modifying an `Nft`'s `name`, `description`, `media_url`, and `attributes` if the provided `Nft` ID matches the one stored in the `Verification` object, and the `Nft` is held within a `Kiosk`. This module heavily relies on an external `launchpad` module (aliased as `0launchpad`) for verification logic.
This package manages `RebelzArt` objects, which are NFTs with a number, image, and dynamic attributes. The `init` function initializes the system by creating `Supply` and `Data` objects, a `ManagerCap` for administrative control, and a `Publisher` object, then shares `Supply`, `Data`, and a `Display` object publicly, and transfers the `ManagerCap` to the deployer. The `set_images` function, callable only by the `ManagerCap` holder, updates the `Data` object's image mappings and the `Supply` object's bitmaps. The `set_traits` function, also gated by `ManagerCap`, updates the `Data` object's labels and values, representing the NFT traits. The `buy_on_curve` and `sell_on_curve` functions allow users to mint or burn `RebelzArt` NFTs based on a bonding curve defined in the `Data` object, which must be set by the `ManagerCap` holder using `set_curve`. The `mint
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.
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": "0xe500132c6dac2f21eae02c1c8103d09f0268995121f0d7df20f83fe84ca90675",
"n_tx": 9988,
"n_successful_tx": 9942,
"n_distinct_epochs": 136,
"n_distinct_sponsors": 1,
"first_seen_cp": 126151237,
"last_seen_cp": 188066880,
"first_seen_ts_ms": 1742814961938,
"last_seen_ts_ms": 1757418900982,
"total_gas_spent_mist": 46328264636,
"n_self_sponsored_tx": 9986,
"n_sponsored_tx": 2,
"gas_price_p50": 740,
"gas_price_p95": 814,
"active_hours_top24": [
11,
18,
19,
8,
21,
9,
1,
16,
2,
10,
12,
20,
13,
17,
0,
23,
14,
4,
7,
15,
22,
3,
5,
6
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail