On-chain properties
Exactly what Hive-Engine stores against this instance. Immutable after mint.
- tokenId
- e2c03748-d24b-4a79-8568-a11adbcd6407
- tier
- Street
- class
- Specialist
- slot
- Weapon
- piece
- 2
- mintedAt
- 2026-09-19T10:18:35.610Z
- batch
- hive-blueprint-v1
Minted 2026-09-19 10:18 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.
- Tier
- Street
- Class
- Specialist
- Slot
- Weapon
- Piece
- 2
- Kind
- fragment
- Minted (app record)
- 2026-09-19T10:18:35.610Z
- Mint status
- minted
mint tx 91ff981e331e89d167d7377ffbe07b2993e9bc64
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.
Observed ownership history
No ownership change has been observed for this NFT since the mirror started watching it. That is not the same as never having moved — changes before the first sync pass are invisible to us, because the chain keeps no transfer history to read.
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":"SYNXFRAGinstances",
"query":{"_id":5}}}'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 2h ago