keysignalOpen scanner

KEYSIGNAL / DOCUMENTATION

Know what the scan sees.
Know what it does not.

A practical guide to network coverage, wallet activity reports, precautionary response steps, score interpretation, and the read-only API.

PRODUCT GUIDE0 SUPPORTED EVM NETWORKSREAD-ONLY
01

Overview

KeySignal checks public transaction history for an EVM wallet address on one selected network at a time. It inspects outgoing transactions that carry signatures and shows the explorer-backed native balance and activity status.

Your wallet never connects. KeySignal does not request a wallet connection, a signature, a seed phrase, or a private key.
02

Supported networks

There are currently 0 configured networks. Network availability is provided by the backend, so this list follows the scanner configuration.

Each scan checks only the selected network. A result on one chain does not report activity from the others.

03

Run a check

  1. 1
    Choose a network

    Select one of the supported networks from the scanner.

  2. 2
    Enter an EVM address

    Paste a public address beginning with 0x. Address contents are public blockchain data.

  3. 3
    Review the report

    The scanner checks up to 200 outgoing transactions and shows whether the explorer returned more history.

For regular accounts, pagination continues until the explorer reports no next page or the 200-transaction scan limit is reached. Smart-contract accounts are marked not applicable to the single-key score.

The homepage also has a live transaction lookup: paste an existing transaction hash to retrieve its indexed sender from the selected network's Blockscout explorer. This checks the explorer record; it does not reconstruct the full public key, connect a wallet, or sign/send a transaction.

04

Understand results

Public key recoverable

An outgoing transaction was present in the checked history. This describes an on-chain signature; it does not mean the account has been compromised.

No outgoing activity found

The selected explorer returned no outgoing transaction in available history. Other networks and off-chain signatures are not included, so this does not prove the key is unexposed.

History incomplete

The transaction limit was reached with older history remaining. The report omits a score rather than treating missing history as safe.

Non-custodial response checklist

When an outgoing transaction is found, the report includes a precautionary checklist for users who independently suspect their private key may be compromised. A recoverable public key is expected after a normal signed transaction; it is not evidence that a private key was exposed or stolen, and the report alone is not a reason to move funds.

The checklist covers creating a fresh wallet with trusted software, securely backing up its recovery phrase, checking assets and networks, and moving assets yourself only if compromise is suspected. KeySignal cannot block transactions, create wallets, or move funds. Checklist progress is held in the current page only and is not saved.

05

Score methodology

The KeySignal score is an approximate information indicator. It is only returned when history is complete. It is not a security assessment or a guarantee.

Starting value100
Outgoing signature observed−20
Transaction countup to −15 · 5 × log10(count + 1)
Age since first observed activityup to −10 · 2 × years
Estimated native balance valueup to −10 · 2.5 × log10(USD / 1,000)
No outgoing transactions in complete history−4 uncertainty adjustment

The score is clamped to 0–100. Tokens are not included, and history from different networks is never combined.

06

API reference

The Next.js server exposes read-only routes:

GET /api/healthService health response.
GET /api/chainsSupported network names, IDs, and native currencies.
GET /api/scan?chainId=8453&address=0x...Scan one supported chain; includes activity, balance, status, and score when available.
GET /api/transaction?chainId=8453&hash=0x...Look up an existing transaction; returns the explorer-indexed sender and transaction link.

Invalid addresses, malformed transaction hashes, and unsupported chain IDs return HTTP 400. Explorer errors return an error response; they are not converted into empty-history or safe results.

07

Privacy & limitations

  • The address is sent to KeySignal and the chosen public explorer to retrieve public chain data.
  • A transaction hash lookup is sent to KeySignal and the selected public explorer; the lookup shows the explorer-indexed sender and does not independently recover a public key.
  • One report covers one selected chain. A wallet key could have signatures on other EVM networks.
  • Bitcoin, Solana, ENS names, tokens, brokerage accounts, and stock holdings are not checked.
  • Off-chain signatures, smart-account authorization methods, and alternative signing schemes are not analyzed.
  • Native balances and estimated values exclude tokens. Pricing depends on the explorer.
  • Public explorer services may delay, limit, change, or fail to serve requests.
  • The response checklist is guidance only; KeySignal cannot block transactions, rotate keys, create wallets, recover keys, or move assets.
  • Checklist progress stays in the current page and is not saved or sent to the server.
  • Reports and scores are informational, not financial, investment, or security advice.
Never share your secret phrase. KeySignal is read-only and cannot access or move assets.
Return to the scanner