Transaction checks on EVM networks and Solana
Templ reads a shared transaction without sending one. Your team sees the chain facts beside the app's report and the check's limits.
EVM transaction checks In testing
Solana transaction checks In testing
Check the networks
| Network | Transaction checks |
|---|---|
| Ethereum | In testing |
| OP Mainnet | In testing |
| BNB Chain | In testing |
| Polygon | In testing |
| Sonic | In testing |
| zkSync Era | In testing |
| Base | In testing |
| Arbitrum One | In testing |
| Avalanche | In testing |
| Linea | In testing |
| Blast | In testing |
| Scroll | In testing |
| Katana | In testing |
| Robinhood Chain | In testing |
| Solana | In testing |
Each network needs its own providers and release checks. A wallet's sign-in network list does not open transaction checks.
Read the parts
- What your app reported holds details the user chose to share.
- What the chain shows holds facts both providers read.
- What Templ thinks holds findings supported by those facts.
- What isn't known lists missing facts and limits.
Your team reads the full check. Users receive approved user-safe facts when your team shares an answer. Team next steps stay private.
Read an EVM check
The check reads transaction status, sender, recipient, value, fees, block and receipt logs. Fee paid is the execution fee: gas used multiplied by the receipt's effective gas price. It excludes other network fees, such as rollup data fees and blob fees. The amount appears only when both providers agree on the receipt facts. It can read token movements, approvals and known contract errors from supported decoding sources. A replay may add a failure reason when the providers can reproduce it. A missing or disputed fact stays unknown.
Read a Solana check
Solana checks In testing
The check reads signature status, slot, fee, error, signers, program logs and token balances. It can compare block height with a shared expiry hint. It does not promise full program decoding or smart-wallet facts. A signature that was not found does not prove the user never sent it.
Use the limits
A funded workspace gets 60 checks per UTC day. Before its first top-up or grant, it gets 15 checks per UTC day. People and AI share this allowance.
A check cannot identify who is chatting, promise fund recovery or prove your app is at fault. Wallet proof is a separate check. Never share a private key or recovery phrase.
Use AI drafts
Sharing a transaction switches AI answers to AI drafts only while the manager keeps that setting on. AI off stays off. The AI cites check facts. Missing evidence goes to your team. AI modes explain the handoff. The Agent API explains citations.
Further reading
- Viewing transactions, Etherscan, published 2022-05-27.
- Transaction confirmation and expiration, Solana Foundation, checked 2026-09-30.
Return to the team inbox.
In testing means the feature is built and not yet open to every workspace.