NFT Explorer

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.

← Blueprint Fragments

Street Enforcer Relic Fragment 2/3

SYNXFRAG #38

Holder, read live just now

burned

Asked api.hive-engine.com/rpc directly for this one instance.

Holder in our mirror

burned

Ownership as of 1h ago

On-chain properties

Exactly what Hive-Engine stores against this instance. Immutable after mint.

tokenId: aa63aee9-e106-42d5-8a9b-3d44a7630585
tier: Street
class: Enforcer
slot: Relic
piece: 2
mintedAt: 2026-09-24T14:50:10.547Z
batch: hive-blueprint-v1

Minted 2026-09-24 14:50 UTC — chain-attested, not our own record.

Our record of this mint

app-recorded

From our own database, not the chain. Shown for context; everything above is independently checkable and this is not.

Tier: Street
Class: Enforcer
Slot: Relic
Piece: 2
Kind: fragment
Minted (app record): 2026-09-24T14:50:10.547Z
Mint status: minted

mint tx 57cbb898f597baa89a0b016dbc503b9cbe9435cc

As it appears in game

app-recorded

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.

Observed ownership history

@affliction→burned
Changed hands between 04:00 and 10:00 UTC on 2 Oct 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.

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":38}}}'

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