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 manages ShipNFT objects, which represent ships with various attributes like rank, name, speed, attack, defense, health, and specializations. The `init` function initializes several shared objects: an `AdminCap` (transferred to a specific address), a `Counter` for generating unique ship IDs, a `MintConfig` (shared), a `PubKey` (shared, with a predefined public key), a `Payout` object (shared, with a recipient address), and a `MintStats` object (shared). It also creates and shares a `TransferPolicy` and a `Display` object for `ShipNFT`s, transferring their capabilities to the same specific address. The `mint_core` entry function allows users to mint `ShipNFT`s. It performs several checks: the minting must not be paused, a public key must be set, the provided timestamp must be in the past, the mint amount must be greater than zero, the signature must be valid and unique, the minter's address must match the one in the signature, and
This package, `testships`, primarily manages `ShipNFT` objects, which represent unique ships with various attributes like rank, name, speed, attack, and defense. The `init` function initializes several shared objects: an `AdminCap` (transferred to a specific address), a `Counter` for ship IDs, a `MintConfig` (initially unpaused), a `PubKey` (with a default public key), a `Payout` address, and `MintStats` to track used signatures. It also sets up a `Display` object and a `TransferPolicy` for `ShipNFT`s, both transferred to a specific address. The `mint` entry function allows users to mint new `ShipNFT`s. It first creates a new `Kiosk` and `KioskOwnerCap` for the minter. It then calls `mint_core`, which verifies a signature against a public key, checks for replay attacks using `MintStats`, ensures the sender matches the signed minter address, and verifies the payment amount. If all checks pass, it
This package implements a staking mechanism for Kiosk items. The primary object type it manages is `Global`, which holds the staking configuration, a table of currently staked items (`staked`), a table of stake counts per staker (`stakes_per_staker`), and a table of supported item types (`supported_types`). Public functions allow users to `stake` an item from their Kiosk into the staking Kiosk, which is finalized by `stake_finalize`. Users can `unstake` their items after a minimum duration. Admin-gated functions (`admin_add_supported_type`, `admin_remove_supported_type`, `admin_purge_if_missing`) manage supported item types and can force-remove orphaned staked items. The package uses dynamic fields (tables) to store staking information and includes time-gating for unstaking based on `min_staking_duration_ms`.
This package manages ShipNFT objects, which represent unique ships with various attributes like rank, name, description, image URL, rarity, type, speed, attack, defense, health, upgrades, specialization, and additional attributes stored in a VecMap. The public entry functions include: - `mint`: Allows users to mint new ShipNFTs. This function creates a new Kiosk and KioskOwnerCap for the minter, then calls `mint_core`. It mutates the Counter, MintStats, and Kiosk objects, and transfers SUI coins to a Payout recipient. It emits a KioskCreated event. - `admin_set_pubkey`: Allows an AdminCap holder to set the public key used for signature verification in the PubKey object. It mutates the PubKey object. - `admin_set_mint_paused`: Allows an AdminCap holder to pause or unpause minting by modifying the MintConfig object. It mutates the MintConfig object. - `update_attributes`: Allows a PubKey holder to update attributes of a
This package, `testships`, manages a primary object type called `ShipNFT`, which represents unique ship non-fungible tokens with various attributes like rank, name, image URL, rarity, type, speed, attack, defense, health, upgrades, and specialization. Public/entry functions include `mint`, which allows users to mint new `ShipNFT`s by providing a valid signature, paying a fee in SUI, and specifying ship details. This function creates a new `ShipNFT`, locks it into a new Kiosk, and transfers the KioskOwnerCap to the minter. It also records the signature in `MintStats` to prevent reuse and emits a `MintEvent`. Other public functions, `admin_set_pubkey` and `admin_set_mint_paused`, are gated by an `AdminCap` and allow an administrator to set the public key used for signature verification and to pause/unpause the minting process, respectively. Notable patterns include signature gating for minting, where a valid ECDSA signature is required, and an allow
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.
botRule-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": "0x495ce5fc99f68d2c8179618e0c4eda72df13efc4c04a6308ba5dc4b2b6ab6597",
"n_tx": 10186,
"n_successful_tx": 10055,
"n_distinct_epochs": 30,
"n_distinct_sponsors": 0,
"first_seen_cp": 205912308,
"last_seen_cp": 263103694,
"first_seen_ts_ms": 1761651049646,
"last_seen_ts_ms": 1775743005416,
"total_gas_spent_mist": 64166757304,
"n_self_sponsored_tx": 10186,
"n_sponsored_tx": 0,
"gas_price_p50": 505,
"gas_price_p95": 505,
"active_hours_top24": [
22,
1,
20,
0,
21,
18,
19,
23,
2,
5,
4,
17,
3,
9,
14,
15,
16,
13,
11,
12,
10,
6,
8
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.9696613
],
"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. Circadian peak → likely N. America (Central–Eastern).
area + brightness = call volume; hover for detail