Blockchains
Bitcoin, Ethereum and Solana, each in its own form.
Screens
What it does
Each blockchain has its own transaction format, so each gets its own form above the same hex view, byte map, Structure and Checks. Bitcoin-family transactions can be edited field by field. Ethereum and Solana transactions are decoded and explained: every field, where it sits in the hex and what a node would refuse. Read a transaction with the wrong blockchain and BScriptView shows where the bytes stop making sense, and offers the one that reads them cleanly.
How it works
Ethereum and Solana transactions are decoded, not checked against the chain: balances, nonces, the base fee and what a contract or program does are not known from the bytes.
Ethereum, every type
Legacy transactions with and without EIP-155, access lists (EIP-2930), EIP-1559 fees, blob transactions (EIP-4844, with or without their blobs) and set-code authorizations (EIP-7702).
The sender, recovered
The sender is worked out from the signature, as block explorers do, and so is the signer of each EIP-7702 authorization; a contract creation shows the address it deploys to.
Call data explained
The selector and each 32-byte word on their own line, with the arguments of well-known functions such as an ERC-20 transfer named and decoded.
Solana, legacy to v1
Legacy, version 0 with address lookup tables, and version 1 (SIMD-0385) with its budget in the header and the signatures last.
Instructions decoded
System, Compute Budget, SPL Token, Associated Token Account and Memo instructions are named, with each account's role; the fee follows from the signatures and the priority fee.
Detects the right one
When a transaction does not decode, every other blockchain is tried and the ones that read it cleanly are offered. Base64 and base58 are turned into hex when pasted.
Good to know
- Bitcoin, testnet / signet, Litecoin, Dogecoin
- Ethereum and other EVM chains by chain id
- Solana legacy, v0 and v1 transactions
- Ethereum and Solana fields are read-only