Tenderly
4 placements on ChainChoice under Tenderly, each scored against its own category's pool and criteria — none currently #1. The placements are not averaged and not ranked against each other: a #1 exchange and a #6 crypto card are two different products in two different markets.
Block Explorers
TenderlyRank#5 OverallScore68
#1 in this category: Routescan
View verdictOnchain Monitoring
Tenderly Monitor / AlertsRank#7 OverallScore62
#1 in this category: Hypernative
View verdictTransaction Simulation
TenderlyRank#7 OverallScore58
#1 in this category: MetaMask Transaction Shield
View verdictRPC & Node Services
Tenderly NodeRank#9 OverallScore45
#1 in this category: BlockPI
View verdictBlock Explorers
How you can lose money here, and what the ranking scores
- Information failure: the number is wrong or bought, or your data leaks.Scored by Data completeness & indexing lag · 26% (Tenderly 4/10)Scored by Independence from the chain · 20% (Tenderly 8/10)
Not assessed by this ranking: Exit failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: What works without paying (30%), Contract verification support (24%).
Onchain Monitoring
How you can lose money here, and what the ranking scores
- Information failure: the number is wrong or bought, or your data leaks.Scored by Verified pre-emptive catches · 40% (Tenderly Monitor / Alerts 2/10)Scored by False-positive honesty and detection method · 20% (Tenderly Monitor / Alerts 6/10)
Not assessed by this ranking: Liveness failure, Exit failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: What it can actually DO (25%), Pricing and procurement disclosure (15%).
Transaction Simulation
How you can lose money here, and what the ranking scores
- Execution failure (Tenderly 2/10): you get a worse price, later, or nothing.Scored by Verifiable performance and what happens when it misses · 25%
- Exit failure (Tenderly 7/10): you cannot get out at par, on time, or with what is yours.Scored by Vendor survival and continuity risk · 25%
- Information failure (Tenderly 5/10): the number is wrong or bought, or your data leaks.Scored by Simulation depth vs. blocklist dependence · 30%
Every failure family that applies to this category is scored. Also scored, as cost, quality or a summary of several families: Published price and true total cost (20%).
RPC & Node Services
How you can lose money here, and what the ranking scores
- Liveness failure (Tenderly Node 5/10): the operator stops, censors you or loses data.Scored by Documented incident record and chain coverage · 25%
Not assessed by this ranking: Exit failure, Information failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: Real cost per 1M identical calls (35%), Archive debug and trace access (20%), Published throughput and self-serve ceiling (20%).