Does a confirmed inscription mean the mint is valid?

No. Confirmation only proves the data is onchain. Ticker uniqueness, supply and holder balances are calculated by the protocol indexer.

Why is there no contract address?

These inscriptions do not have a mint contract. The inscription payload itself is the transaction calldata.

Can I close the page during a batch?

Do not close it if you want the local queue to continue. Transactions already broadcast remain onchain and cannot be cancelled by closing the page.

EVM Inscriber

Put UTF-8 text or hex data into transaction calldata and send it from your wallet. A confirmed transaction only proves the data is onchain; the protocol indexer decides whether the inscription is valid.

A confirmed transaction only means the data is onchain; the protocol indexer determines whether the inscription is valid.

Inscription Data

Encoded as exact UTF-8 without reformatting JSON, reordering keys or adding characters.

Inscription Template

Inscription Content

59 bytes · 64 KB max

Transaction Preview

Review the destination, complete payload and estimated fee before signing.

Sending Wallet: Not connected
Receiving address: This wallet
Attached Amount: 0 BNB
Wallet balance: —
Estimated Gas: Estimated by wallet
Estimated Gas Used: —

Each wallet reads its pending nonce once, broadcasts every transaction with the next nonce, then waits for all receipts together.

Final Calldata

0x646174613a2c7b2270223a226273632d3230222c226f70223a226d696e74222c227469636b223a2247544b31222c22616d74223a2231303030227d

Content Hash：0x76df63463b9c25e0e132df35932ed8adc3feb6c91f2ab27a5f47453322028514

Local Execution History

Only transactions started in this browser are recorded. Use the transaction hash and block explorer receipt as the source of truth.

Transactions will appear here after you start.

EVM inscriber — write text into transaction calldata

An EVM inscription does not call a mint contract. The inscription is the transaction calldata itself. This tool preserves UTF-8 text or hex data exactly, shows the final payload, content hash, sender and estimated gas before signing, and supports both single-wallet repeats and local multi-wallet batches.

Input: UTF-8 text or hex calldata
Destination: the sending wallet by default, with 0 native coin attached
Fee: network gas only — no platform fee
Validity: determined by the relevant inscription protocol indexer

How it works

1. Compose the payload
Enter plain text, a protocol JSON template or raw hex. The tool does not compact JSON, reorder keys or add prefixes automatically.
2. Review the exact calldata
Check the full payload, byte count, content hash, sending wallet and gas before signing. Onchain inscription data cannot be edited later.
3. Sign and wait for the receipt
Single-wallet mode uses the connected wallet. Batch mode signs locally with wallets from the encrypted wallet vault and never uploads private keys.

FAQ

Does a confirmed inscription mean the mint is valid?: No. Confirmation only proves the data is onchain. Ticker uniqueness, supply and holder balances are calculated by the protocol indexer.
Why is there no contract address?: These inscriptions do not have a mint contract. The inscription payload itself is the transaction calldata.
Can I close the page during a batch?: Do not close it if you want the local queue to continue. Transactions already broadcast remain onchain and cannot be cancelled by closing the page.