On-chain properties
Exactly what Hive-Engine stores against this instance. Immutable after mint.
- rarity
- racket
- attributes
- intel,contraband
- mintedAt
- 2026-07-13T09:37:20.757Z
- batch
- 1
Minted 2026-07-13 09:37 UTC — chain-attested, not our own record.
Our record of this mint
app-recordedFrom our own database, not the chain. Shown for context; everything above is independently checkable and this is not.
No matching record. The NFT exists on chain regardless — our database is not what makes it real.
As it appears in game
app-recordedThe same card players see. Its class, slot, tier, passive and stat roll are read from the chain properties above, but the item's name is assigned by our catalog rather than minted into the NFT, and the stats are shown at level 1 — levelling is recorded by us, not on chain, so a held item may be stronger than this.
This collection has no in-game card — a turf plot is a place on the map rather than an item held by a crew.
Observed ownership history
Changed hands between 19:10 and 19:20 UTC on 28 Sept 2026 (10 minutes window)
Each row is a range, not a moment. Hive-Engine records who holds an NFT now, not how it got there, so all we can honestly say is that the holder differed between two of our checks. This collection is checked every 10 minutes — if an NFT changed hands twice inside one of those windows, the two moves appear here as one and the middle holder does not appear at all.
Check this yourself
The holder and properties above come from one public call. Make it yourself:
curl -s https://api.hive-engine.com/rpc/contracts \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"find","params":{
"contract":"nft","table":"TURFinstances",
"query":{"_id":83}}}'The account field is the holder and properties is the property table. What that call will not give you is history — the contract stores only the current state, which is why the timeline above is a record of our observations rather than a transfer log.
Mirror freshness: Ownership as of 20h ago