unseal▰
sBPF intelligence, from the inside out ↗

Look beneath
the interface.

Every interaction starts with code.
See who can change it. Trace what your wallet touches.
Inspect the bytes behind the promise.

NNVDAx Selected quote assetPair asset details ↗
unseal / loader_v3ACCOUNT STRUCTURE / READ-ONLY
01// UNSEAL · loader-v3 account inspection
02pub fn decode_program_data(data: &[u8]) -> Result<ProgramData> {
03 require!(data.len() >= 45, InvalidAccountData);
04 let discriminator = u32::from_le_bytes(data[0..4].try_into()?);
05 require!(discriminator == 3, InvalidAccountType);
06
07 let slot = u64::from_le_bytes(data[4..12].try_into()?);
08 let authority = match data[12] {
09 0 => None,
10 1 => Some(Pubkey::new_from_array(data[13..45].try_into()?)),
11 _ => return Err(InvalidAuthorityFlag),
12 };
13
14 let binary = &data[45..];
15 let elf_magic = [0x7f, 0x45, 0x4c, 0x46];
16 let has_elf = binary.starts_with(&elf_magic);
17
18 Ok(ProgramData {
19 last_deployed_slot: slot,
20 upgrade_authority: authority,
21 allocated_bytes: binary.len(),
22 elf_detected: has_elf,
23 })
24}
6programs in the directory
8recent wallet transactions traced
64bit ELF binary inspection
0transactions to sign
01 / ON-CHAIN INTELLIGENCE

Who holds
the rewrite key?

A program can look the same while its code changes underneath. Read its loader, deployment slot and upgrade authority directly from Solana.

PROGRAM INSPECTORMAINNET / READ-ONLY

Choose a program below or paste its address.

◇

Start with the program. Follow the evidence.

No scores guessed. No wallet permissions requested.

AWAITING INPUT
02 / YOUR WALLET

Know what
you’ve touched.

Read your eight most recent transactions. See which programs appear in successful calls, including inner instructions, then inspect their authority.

Public addresses only. No connection or signature.

Your results appear here.

ANALYSIS

Watch the record
come into focus.

Raw account bytes on one side. The controls they encode on the other.

Reading mainnet

pump.fun

Resolving program metadata…
—allocated binary
—upgrade authority
—ELF header
ACCOUNT STRUCTURE SELECT A FIELD
RAW ACCOUNT BYTES PROGRAM HEADER
Waiting for the RPC response…
DECODED METADATA PARSED
The next record appears here.
Public mainnet account data · read-onlyInspect another program ↗
03 / THE WORKBENCH

From opaque bytes
to something readable.

Open an ELF64 binary or inspect raw instruction bytes. Decode supported sBPF v0 instructions and explore the file structure, right in your browser.

BINARY LENSINSTRUCTION REFERENCE
Files stay on your device · max 16 MB
Static inspection, not execution. Unknown opcodes remain visible.sBPF v0 / ELF64 LE
EVIDENCE, NOT A BLACK BOX

A clear path
back to the source.

An authority address is evidence of upgrade control—not a security verdict. Every inspection includes a slot and an explorer link so you can check the record yourself.

Read the Solana loader documentation ↗
unseal
drag to arrange · click to inspect
Select a node to follow the evidence.
THE PROCESS

Open the record.
Keep the context.

01

Resolve the account

Read public mainnet data, identify the loader and follow the ProgramData address where available.

getAccountInfo(program)
02

Expose the controls

Surface the authority and deployment slot. Distinguish revoked authority from unsupported metadata.

authority ≠ a safety score
03

Inspect the binary

Explore ELF sections, readable strings and supported instruction encodings. Export the result for deeper analysis.

bytes → structure → evidence
PROGRAM DIRECTORY

Choose your entry point.

Directory entries are program IDs, not audit endorsements. Status is fetched when you inspect.

LESS BLIND TRUST.

More to look at.

The interface is only the surface. Start underneath.

Unseal a program ↗
SCOPE & LIMITATIONS

What UNSEAL reads.

Program inspection uses public Solana RPC endpoints. Loader-v3 authority metadata is parsed from ProgramData; unsupported loaders are marked as such.

Wallet tracing covers up to eight recent signatures. Unavailable and failed transactions are reported, not interpreted as a clean bill of health.

The local workbench supports ELF64 little-endian files and common sBPF v0 encodings. It does not execute programs, recover verified Rust source, audit a contract or replay transactions. AI reconstruction is not connected.

Public RPC providers may rate-limit requests. Inspection results describe the returned slot, not future program behavior.