Cronos rollback: Did your deal disappear? How to check the balance

Detailed explanation of the Cronos Chain Rollback Event on August 30, 2026: Affected Time Window, Self-Inspection Guidelines and Risk Warnings

If you sent a transaction to the Cronos Chain between 12:38 and 14:33 Coordinated Universal Time (UTC) on August 30, 2026, the transaction no longer exists today. Your balance will return to the state it was before that time period. For most holders, this is not a forfeiture of assets, but a complete reversal: any funds issued during this period have never been deducted from the account. However, in some cases, this does lead to material losses. This article will clarify the specific time window affected, guide you on how to check your transaction records in a matter of minutes, and point out where the boundaries of "security confirmation" are.

What happened to the Cronos chain on August 30, 2026

On September 8, 2026, the Cronos team released a Post-mortem report on the attack on the loan agreement Tectonic. The post-event investigation report is a retrospective investigation document conducted by the project party on emergencies. It is in this report that previously missing key data are presented.

According to the report relayed by the trade publication Cointelegraph, the attacker's sequence of action was as follows: They pushed the price of TONIC tokens nearly 300 times higher in a thinly liquid trading venue. Lending agreements allow users to lend money against collateral and continuously value the collateral through a Price Feed. The attack targeted this valuation mechanism. Taking advantage of artificially high collateral values, the attackers lent $120.4 million in nine lending markets and completed them in eleven transfers. Its initial principal amount is approximately US$5 million.

The report states that the incident was discovered at 12:49 UTC. At 14:32:47 UTC, the network stalled. Developers described it as "a difficult decision made with the validator, weighing the user's expectations for chain finality against the funds at risk." Verifiers are the operators who propose and confirm blocks; on a chain of only a few dozen such operators, reaching a coordinated agreement is technically feasible.

We described the network outage in our August 31 article "Cronos suspends chain services after Tectonic vulnerability exploitation", which ended in shutdown because the post-mortem investigation report had not yet been released. This article provides the final solution.

Which time windows were erased

The block is a set of blockchain transaction packages recorded in a fixed order. Rollback is the process of co-resetting the chain to an earlier block: anything confirmed thereafter is discarded, and the chain starts building again from that point.

According to its own statement, Cronos dropped 10,961 blocks. This is equivalent to 1 hour and 54 minutes of chain history. What's important to you is a sentence in the post-mortem report: Every transaction in that window is reversed, whether or not they are related to an attack. At the time of chain restart, open positions in the running application were re-priced.

In terms you can understand: the reset point is located in the block carrying the timestamp of August 30, 2026 12:38:55 Coordinated Universal Time. Downtime began at 14:32:47 UTC. All content in between is discarded. Block production did not resume until 23:49:01 UTC that day, about eleven hours before the reset point.

Does your balance disappear after rollback?

In the basic case, the answer is no. Your balance has been reset to 12:38:55 UTC on August 30, 2026. A transfer you sent at 13:10 UTC disappears, followed by the corresponding deduction. A redemption you made at 14:00 UTC never occurred, so you re-hold the original token. Funds that were present at your address before 12:38:55 UTC remain there unchanged.

However,"security confirmation" has boundaries, which is the real reason for writing this article:

• You receive a payment within the window period and deliver the goods or services accordingly. The payment no longer exists; however, your delivery still exists.
• You have connected the value bridge to another chain during the window period, and the other chain has received it. Rollbacks cannot retrieve the value that has left the chain.
• You have an open leveraged position. When the chain is restarted, it will be revalued based on changing prices.
• You make deposits to the exchange during the window period. A separate ledger system applies there, as will be described in detail below.
• You recorded a tax-related disposal, but it no longer exists on the chain today. Your record will then disagree with the data on the chain.

The post-action report itself points to an important practical limitation: According to Cronos, reversed transactions can only be tracked through archived records and are no longer visible through public blockchain browsers. Therefore, anyone who needs proof should build evidence based on their own documents.

The chain is still running, but the links in the middle have been recasted: this is exactly what happened to Cronos on 10,961 blocks.

How to check your Cronos transactions in minutes

Checks require no expertise or additional tools. Block Browser is a website that makes current blockchain content searchable. The key to understanding it is: It shows you the current chain, the rebuilt version.

Step 1: Open your address
Visit the official Cronos Explorer and enter your payment address. You don't need to connect to your wallet or enter a private key. The address is a public identifier; no one searching for it can move the funds in it.

Step 2: Narrowing the scope
Check the transaction list around August 30, 2026. The key time window is from 12:38:55 to 14:32:47 UTC. Please switch to your time zone; at Central European Daylight Saving Time (two hours fast), this window is approximately between 14:39 and 16:33.

Step 3: Check for missing items
If no entry is found in this window, your address is not affected. If you remember that there was money flowing during that period but cannot find it now, the flow has been discarded. Funds that would have been transferred have returned to their original locations.

Step 4: Save your evidence
Save the transaction hash (the unique identifier of your transfer), as well as the timestamp and amount from your wallet history or confirmation email. If you have to explain to a counterparty, exchange or tax bureau why an event is missing from the chain, these records are your only evidence.

What cannot be technically retrieved by rollback

The limitations of such resets extend well along chain boundaries. Blockchain can only rewrite its own history. Once value moves to another chain through the bridge, there is an independent and valid event there that is outside the control of the reset chain. Bridging applications transfer value from one blockchain to another by locking on one chain and issuing on another chain.

This is exactly what happens here. According to post-event reports,$9.19 million had left the chain before the outage, accounting for 7.6% of the total affected. These funds are considered unrecovered.

Cointelegraph quoted data from data service provider Bitquery as saying that the share of the Ethereum blockchain was traced to US$8.3 million. As a result, the reversal reversed $111.2 million, but failed in the remaining portion.

For holders, a sober rule follows: as long as the event does not leave the chain, reset only protects you. How this intervention works in principle, and what cases it covers, we have described at a general level in the article "What happens to your tokens when the chain is rolled back". The Cronos case is the first major application of the mechanism this year.

Gaps are measurable in the chain itself

You don't have to trust the numbers of the project party completely. The incident left a mark that anyone could measure with a simple query. We did this through the chain's public access point at approximately 00:40 UTC on September 10, 2026.

The chain ID is 25 (Cronos main network) and the height is 92,926,013 blocks. Block number 90,896,189 carries a timestamp of August 30, 2026 at 12:38:55 UTC. Immediately following, block 90,896,190 carries a timestamp of August 30, 2026 at 23:49:01 UTC. As a result, there is a gap of 11 hours, 10 minutes and 6 seconds between two consecutive blocks, compared to a few seconds normally. This jump was caused by the shutdown.

The second measurement is more convincing. The report shows that the height at which the chain was halted is block 90,907,150. On today's chain, this block carries a timestamp of 05:59:27 UTC on August 31, 2026. Therefore, it was created approximately 15 hours after the attack occurred. These block heights are obviously regenerated. Users saw that the confirmed branch on August 30 had disappeared from today's chain.

Anyone who wants to verify arithmetic calculations does not need an account or subscription. You only need two block numbers and their timestamps, both of which can be obtained from any public browser.

Beyond chain boundaries, the effectiveness of any reset ends: US$9.19 million is considered unrecovered.

If your exchange deposit falls within the window period

The trading platform keeps its own account book and credits the deposit after the set confirmation number is reached. After that, they kept accounts internally and no longer moved the consulting chain every time. If the chain is subsequently reset, a credit may exist alone without its underlying transaction. Conversely, a withdrawal that reaches you may be missing on the chain.

In this case, please stick to three sobering suggestions. First: Do not send any more funds until the position is clarified. Double payments are the most common chain damage after such incidents. Second: Save the transaction hash, timestamp, and amount before contacting customer support. Third: Compare today's position in your exchange account with your last record before August 30. If you regularly buy through trading platforms, our comparison of the best cryptocurrency exchanges lists the number of confirmations required for each provider.

A bit of background, lest anyone draw the wrong lesson: the incident was a chain incident, not a failure of individual providers. The reason why the exchange corrected its deposits after rolling back was because of the lack of underlying bookkeeping.

Conflict between finality and rescued funds: The contradiction pointed out by Cronos himself

Finality is the chain's promise that confirmed transactions will not be reversed. This commitment is the fundamental reason why blockchain is suitable as a settlement layer. Rollbacks suspend this commitment for specific windows.

It is worth noting that the project party itself publicly pointed out this conflict. In the quoted paragraph above, Cronos clearly compared the finality of opposing user expectations with the money at risk and called the decision difficult. As a result, this trade-off is documented rather than disappearing behind successful notices.

Whether the operator agrees that the chain of history can be rolled back can still be credibly fulfilled is a matter of judgment. Numbers alone cannot solve this problem, and this article does not intend to solve it. The verifiable fact that can be recorded is that the intervention was possible, it was executed, and it was effective for approximately $111 million. Anyone deriving expectations for future events from them is making his own assessment, not a statement of discovery.

Impact of this case on your own custody

The obvious lesson seems to be that self-custody is not helpful here. This is true, but it also shows what self-hosting is actually guarding against. Whoever holds his own key can protect against the custodian's bankruptcy and third-party access to his account. No key protects against rule changes in value on the chain because the key only proves ownership, not the state of the chain.

There are two conclusions in practice. First of all, it is not recommended to permanently leave large positions in a single chain with limited operator circles. Second, your own bookkeeping is more important than many people think: transaction hashes, timestamps, and wallet statements are the only evidence of survival after such interference. If you store your keys separately from your daily devices, our Hardware Wallet Comparison lists the differences between different devices.

Another point is easy to overlook in excitement: After a network outage, the chain becomes unreliable for hours. Making time-sensitive payments on the chain that has just been stopped is an avoidable risk in the following days.

Check for Cronos Rollbacks: Summary of Points

First check if you are affected.
Open your address in your browser and see if there are any entries in the window from 12:38:55 to 14:32:47 UTC on August 30, 2026. If you make deposits to a trading platform during this period, please check your positions there with your records; the number of confirmations required by each provider is listed in Exchange Comparisons .

Save your records before doing anything else.
After reset, since the dropped event no longer appears in the public browser, the transaction hash, timestamp, and amount from wallet history are the only evidence. The most secure locations for your keys and history are displayed in Hardware Wallet Comparison .

Spread large positions across multiple chains.
This incident shows that the risk lies not only with the custodian, but also with the chain itself. Which wallet can cleanly run multiple networks in parallel, and what the daily differences are detailed in Software Wallet Comparison .

(As of September 10, 2026. This article does not constitute investment advice. Price and fee structures are subject to change; please check terms with your provider before purchasing.)