DNA ProtocolTransparency
XRPL TESTNET
TRANSPARENCY STARTS WITH CONTEXT

Look beyondthe hash.

01 / OBSERVE

What is public.
What is structured as ciphertext.
What remains unproven.

One transaction. Three perspectives.
TRANSPARENCY WORKSPACEPUBLIC EVIDENCE / NO DECRYPTION
THE ANATOMY OF A BOUNDARY
INTERACTIVE SCHEMA ILLUSTRATIONNOT A LOOKUP RESULT

Encrypted does not mean invisible.

Ciphertext is still stored on a public ledger. Its format is inspectable; its confidentiality is not established here.

START AN INSPECTION 01 / 01

A hash is your
starting point.

Follow a real transaction from the public record to its supported packet structure.

/

64 hexadecimal characters. No keys or personal data.

Or begin with a published record
Read-only
No wallet needed

Your public hash is sent to this site's API and the Testnet node. Recent inspections stay in page memory only.

DESIGNED TO CLARIFY. NOT TO CERTIFY.Open the DNA Proof Feed
THE METHOD / NOT THE MARKETING

Evidence, with
the edges included.

01

Read what the ledger says.

Request the actual Testnet transaction. Check validation and execution status before interpreting the packet.

02

Separate the visible layers.

Inspect public fields, format metadata and the ciphertext segment. Every on-ledger byte remains publicly accessible.

03

Keep the unknowns visible.

No decryption, privacy certification, identity check, ZK proof verification or signature verification is performed.

Format is observable.
Confidentiality is not a checkbox.

Public addresses, timestamps and hashes can reveal or link information. A recognized encryption envelope does not prove anonymity, consent, secure key handling or the absence of personal data.

KNOW THE
BOUNDARY.
TRANSPARENCY / SCOPE

A clear view.
With clear limits.

DNA Protocol Transparency is a read-only inspection tool for supported DNA Protocol transactions on XRPL Testnet.

01

What is inspected

Ledger validation, public transaction fields, packet framing, and the structure of the publisher's encrypted-payload format. The published feed is compared where available.

02

What is not verified

No decryption or authentication-tag verification is performed. This tool does not establish confidentiality, secure key handling, absence of personal data, anonymity, identity, consent, a valid ZK proof, or a valid signature.

03

Where data comes from

The transaction is requested from XRPL Testnet. Profiles and batch labels come from the DNA Proof Feed. Synthetic-input labels come from reviewed publishing metadata, not the ledger. Unrecorded sources stay unknown.

04

Your lookup data

Your public transaction hash is sent to this site's API and the Testnet node. No wallet, files, keys or genomic inputs are requested. No analytics are added and recent lookups stay in memory. Hosting and RPC providers may retain request logs.

All on-ledger bytes are public, including ciphertext and published plaintext hashes. Hashes can be linkable or susceptible to guessing. Unknown memo contents are not exposed by this interface. Testnet history and upstream services may be unavailable.