Cooldown Active Error Explainer

WHAT IT DOES

Cooldown Active Error Explainer takes a pending or recent transaction hash and determines whether the sender is still within a cooldown period enforced by the target contract. Many EVM contracts implement cooldown mechanisms to prevent rapid repeated actions—for example, limiting how often a user can claim rewards, withdraw funds, perform a governance vote, or call a sensitive function. If a cooldown is active, the transaction will revert with an error such as "Cooldown: not ready" or "Too early to call again." This tool reads the transaction's target contract and sender, then queries common cooldown view functions such as lastAction(), cooldownDuration(), getCooldownEnd(), isCooldownActive(), and cooldownRemaining(). It computes the cooldown expiry time (last action + duration) and compares it against the current block timestamp. The output includes the last action timestamp, the cooldown duration, the expiry time, the remaining time (in seconds and human‑readable format), and a plain‑language explanation of whether the transaction will fail and what the user should do—typically, waiting for the cooldown to expire.

HOW TO USE

Paste any transaction hash into the input field, select the network, and click "Check cooldown". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the transaction details and the target contract's cooldown state. It attempts multiple common cooldown function signatures (lastAction, cooldownDuration, getCooldownEnd, isCooldownActive, cooldownRemaining) to maximize compatibility with different contract implementations. It fetches the current block timestamp to compare against the cooldown expiry. Historical cooldown events are fetched in chunks (500 blocks per request) with automatic backoff and halving on failure to avoid public RPC caps. The AI layer generates a plain‑English summary: whether the cooldown is active, when it will expire, and what action the user can take. A progress bar visualizes the cooldown elapsed time. You can click on the transaction hash or contract address to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR COOLDOWN EVENTS

Cooldown state is often tracked via storage, but historical events (CooldownStart, CooldownReset, CooldownExpired) provide valuable context—for example, whether the cooldown was recently reset or extended. However, public RPCs aggressively cap eth_getLogs block ranges; a full‑range request over 10,000 blocks will fail with a "block range too large" error. This tool automatically chunkes log requests into 500‑block slices to stay within safe limits for all major RPC providers. If a chunk fails (due to timeout or provider‑specific caps), it halves that chunk and retries recursively—ensuring that even with aggressive caps, the tool reliably retrieves all relevant cooldown events. The tool also caches the current block timestamp at the start of the scan to maintain consistency across all calculations and event fetches, preventing off‑by‑one errors when the chain advances during the scan.

WHAT IT CANNOT SEE

This tool cannot detect cooldowns that depend on off‑chain state (e.g., cooldowns that are enforced by an off‑chain relayer or based on external data feeds). It cannot predict future cooldown expirations that might occur before the transaction is mined—the check reflects the current block, not the future. It cannot verify that the sender intended to wait for the cooldown—the tool reads what is on‑chain, not the user's intent. It cannot detect cooldowns in contracts that use non‑standard patterns (e.g., cooldowns that are not exposed via view functions, or cooldowns that are calculated using complex logic not easily queryable). It cannot guarantee that a retry will succeed even if the cooldown appears to have expired, as other conditions may also need to be met (e.g., balance, allowance, paused state). It cannot detect if the cooldown is a security measure or a temporary throttle—this tool only checks whether the cooldown is active based on current state, it does not assess intent or risk. It also cannot detect cooldowns that are enforced at the proxy implementation layer without being exposed through the proxy's own interface.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche C‑chain, etc.) and relies on standard cooldown function signatures (lastAction, cooldownDuration, getCooldownEnd, isCooldownActive, cooldownRemaining). It does not support custom cooldown logic that does not expose these functions as public view methods. All explanations are AI‑generated from data the app reads on‑chain—the AI synthesizes the cooldown state, last action time, duration, and transaction context into plain English, but it does not have special access to private contract logic or off‑chain data. Always review what you are actually signing in your wallet before approving any transaction; a cooldown check does not replace your own verification of the transaction details, including the target contract and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.