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 `Stake` objects, which represent staking pools for NFTs, and `CreateStakeCap` objects, which grant permission to create and manage these pools. Public/entry functions allow authorized users (holding a `CreateStakeCap`) to create new `Stake` pools, update their staking period or start/end timestamps, and add liquidity to the pool. Users can stake NFTs into a `Stake` pool, provided the pool is active and the NFT type matches, and claim their staked NFTs and a proportional share of the pool's liquidity after the staking period ends. The package uses dynamic object fields to store the staked NFTs and the pool's coin.
This package manages `Stake` objects, which represent staking pools for NFTs, and `CreateStakeCap` objects, which grant administrative privileges. Public/entry functions allow creating new `Stake` pools with an initial coin amount and a specified NFT type, updating the staking period or start timestamp of existing pools, and adding more liquidity to a pool. Users can stake NFTs into a `Stake` pool, receiving a `StakeItem` object, and later claim their staked NFT along with a proportional share of the pool's coin liquidity, provided the staking period has ended. An `unlock_pool` function allows the `CreateStakeCap` holder to remove a staked NFT and distribute its share of the pool's liquidity, regardless of the staking period. The package utilizes dynamic object fields to store the staked NFTs and the pool's coin within the `Stake` object, and events are emitted for staking, claiming, and creating stakes. Access to `create_stake`, `update_period_pool`, `update_timestamp_pool`, `add_liquidity_pool`, and `unlock
This package primarily manages an `ExecuteCap` object, which appears to be an admin capability. The `init` function creates and transfers this `ExecuteCap` to the deployer. Public entry functions include `claim_bridge_nft`, which transfers an arbitrary object (`Ty0`) to a specified address and emits a `ClaimBridgeNFTEvent`, and `reward_winner_lottery`, which emits a `WinnerLottery` event with details about a lottery winner. The `buy_ticket` function splits a coin of type `Ty0` and transfers the split amount to a specified address, then emits a `BuyTicket` event. Similarly, `reward_winner_ticket` splits a coin and transfers it to a recipient, emitting a `RewardWinnerTicket` event. Notably, `claim_bridge_nft`, `reward_winner_lottery`, and `reward_winner_ticket` are gated by the `ExecuteCap`, indicating administrative control over these reward mechanisms.
This package manages an `ExecuteCap` object, which acts as an administrative capability. The `init` function creates and transfers this `ExecuteCap` to the package deployer. Public/entry functions include `claim_bridge_nft`, which transfers a generic object (`Ty0`) to a specified address and emits a `ClaimBridgeNFTEvent`, and `reward_winner_lottery`, which emits a `WinnerLottery` event. `buy_ticket` allows users to buy a lottery ticket by splitting a Coin and transferring it to a pool recipient, emitting a `BuyTicket` event. `reward_winner_ticket` splits a Coin and transfers it to a recipient, emitting a `RewardWinnerTicket` event. The `ExecuteCap` is used to gate the `claim_bridge_nft` and `reward_winner_lottery` functions, indicating an admin-controlled action.
This package defines a single object type, `MEO`, which is a dummy struct. The `init` function creates a new fungible token called "Nikka" (symbol "NKC") with 9 decimal places and a total supply of 30,000,000. It then mints this initial supply to the transaction sender. Finally, it freezes the `CoinMetadata<MEO>` object and transfers the `TreasuryCap<MEO>` to a hardcoded zero address, effectively burning the minting authority. There are no public or entry functions beyond the `init` function. The package utilizes the `coin` and `transfer` modules for token creation and distribution, and `url` for metadata.
area + brightness = call volume; hover for detail
{
"wallet": "0xb6e3526267d88cdddece265b6d94b5612dc813ec7f116715c535eab4bfba8692",
"n_tx": 201,
"n_successful_tx": 200,
"n_distinct_epochs": 16,
"n_distinct_sponsors": 0,
"first_seen_cp": 1580610,
"last_seen_cp": 10098507,
"first_seen_ts_ms": 1683129592526,
"last_seen_ts_ms": 1691790670665,
"total_gas_spent_mist": -233353044,
"n_self_sponsored_tx": 201,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
3,
12,
6,
15,
8,
20,
7,
13,
14,
11,
17,
5,
4,
16,
10,
23,
21,
1,
9,
18
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.