Every Turf plot, equipment piece, blueprint and fragment is a Hive-Engine NFT. Everything here is read from the chain — you can verify any of it yourself.



Asked api.hive-engine.com/rpc directly for this one instance.
Exactly what Hive-Engine stores against this instance. Immutable after mint.
Minted 2026-09-27 03:33 UTC — chain-attested, not our own record.
From our own database, not the chain. Shown for context; everything above is independently checkable and this is not.
mint tx 97649c7dc47c1b849b111504d68407e456df1bec
The 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.



Changed hands between 04:00 and 10:00 UTC on 27 Sept 2026 (6 hours 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 6 hours — 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.
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":"SYNXFRAGinstances",
"query":{"_id":51}}}'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 1h ago