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 primarily manages an NFT object type, which has fields for a unique ID, name, description, and image URL. The `init` function initializes a `Publisher` object and a `Display<NFT>` object, setting up display properties for the NFT, and then transfers both to the transaction sender. The `mint` entry function is a stub and currently does nothing, effectively consuming its arguments and returning. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties implemented in the provided bytecode.
This package defines an `NFT` object with `id`, `name`, `description`, and `img_url` fields. The `init` function creates and transfers a `Publisher` object and a `Display<NFT>` object to the transaction sender, initializing the `Display` object with metadata fields for `NFT`s. The `mint` entry function is a no-op, taking various byte vectors and an address but performing no operations or mutations. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties implemented.
This Sui package, FUDDIES, primarily manages `NFT` objects, which represent non-fungible tokens with fields for `id`, `name`, `description`, and `img_url`. The `init` function initializes a `Publisher` and a `Display<NFT>` object, transferring both to the transaction sender. The `mint` entry function creates a new `NFT` object using provided name, description, and image URL, emits an `NFTMinted` event containing the NFT's ID, creator, and name, and then transfers the newly minted `NFT` to a specified recipient address. A notable pattern is the use of `display::new_with_fields` to create a `Display` object for the `NFT` type during initialization, and a check in the `mint` function that appears to be a gating mechanism, though its exact condition (`Arg3 != "0x0d2323692c2"`) is unusual and might be a placeholder or specific signature.
casualRule-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": "0x8b7ac13b1264b64bec9b797d76e71be7eb51a5558ad23276854f6faa6c8ca299",
"n_tx": 3,
"n_successful_tx": 3,
"n_distinct_epochs": 2,
"n_distinct_sponsors": 0,
"first_seen_cp": 1656157,
"last_seen_cp": 1748184,
"first_seen_ts_ms": 1683207372705,
"last_seen_ts_ms": 1683302233171,
"total_gas_spent_mist": 59869640,
"n_self_sponsored_tx": 3,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
15,
13
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC.