Decode any Solana error in seconds
Paste custom program error: 0x1771, an Anchor log, or a failed signature. Get the program, the variant name, why it happened and how to fix it.
Developer tools
All tools →Paste "custom program error: 0x1771" or any Solana error and get the program, variant, cause and fix.
Paste a signature and see every instruction, account, log line and the exact reason a transaction failed.
Derive program derived addresses from seeds with typed inputs. Shows the bump and the exact bytes used.
Paste a mint address and see its extensions, authorities and transfer fees in plain language with risk flags.
Rent-exempt minimum for any account size, with presets for token accounts, mints and Anchor accounts.
Compute unit limit × micro-lamport price = total fee. Understand what you actually pay per transaction.
Convert between lamports and SOL instantly, with the math shown.
Check whether a string is a valid Solana address, whether it is on the ed25519 curve, and what lives there on-chain.
Most searched errors
Full error index →A custom program error is a u32 returned by the program that ran. The same number means different things in different programs: 0x1 is “insufficient funds” in SPL Token and “not enough SOL” in the System Program.
Anchor reserves 100–5999 for framework errors and starts each program’s own error enum at 6000 (0x1770). So 0x1771 is the second variant of the program’s #[error_code] enum.
Production builds throw Solana error #8100002 and tell you to run npx @solana/errors decode. Paste that whole line above: the code and its base64 context are decoded here, no terminal needed. All Kit codes →