Switch recorded views. No live replay.
The earlier transaction
An approval-shaped input
AMOUNT IN THE INPUT
The next transaction
Original history:
Opening the recorded inspection…
Read the case note ↗Recorded data unavailable.
The inspection export is missing, altered or inconsistent. No result can be displayed.
Try reloading this page. No result is displayed unless the recording passes its integrity checks.
ONE CHANGE IN REAL BLOCKCHAIN HISTORY
What if one amount
had been zero?
One earlier amount set to zero. The next transaction went from success to revert in the recorded replay.
Explore a recorded replay. The real chain stays untouched.
What could this be useful for?HOW FAR DID THE CHANGE REACH?
Opening this demo performs no fresh replay or independent verification. The real chain was not changed.
What does your next move depend on?
A transaction can succeed in real history — and revert when one earlier input changes.
RHOOK asks that “what if?” question in an alternative replay. Here, the next transaction changed while 278 other downstream results stayed the same.
A wallet, app or automated agent could use verified alternatives to investigate what an action depends on. This demo shows that underlying capability on one fixed historical case.
The exact internal revert cause is not established. This case does not prove a token balance or protect a live wallet.
One outcome changed.
278 kept their result.
Of 279 later events, one changed from success to revert. Only that transaction has a separately recorded verified Claim.
Explore all 279 later events
50 blocks321 total arrivals41 before + 1 target + 279 downstream0 unresolved
DOWNSTREAM LIFECYCLE MAP Changed Unchanged
Each square is one arrival. This map is local lifecycle inspection, not 279 independently verified Claims.
| Transaction | Actual | Branch |
|---|
No arrivals match this search. Try a transaction locator or clear the filter.
How do we know?
Two different native implementations agreed on the alternative. One Claim was verified under a pinned profile. This page displays that record.
Read the case note ↗Explore the source ↗
Inspect the recorded Claim and checks
BRANCH PROTOCOL 0.2
SUCCESS REVERTRECORDED · ACCEPTED
Acceptance establishes this negative answer under the profile. It does not mean the branch transaction succeeded or authorize an application action.
Query / Claim / Envelope JSON
The export is not a standalone verification package. Original Packet and admitted world context are not included.
9 / 9 dischargedUNDER PROFILE
All nine coverage obligations were discharged in the recorded verification. Expand an obligation to see its exact check identifiers.
HOW THIS ANSWER WAS ESTABLISHED
Exact trust assumptions
Archive and Packet SHA-256 pins
Independent context import is unsupported by this preview. A complete independent verification would require the original Packet, admitted acquired-world context and authenticated verifier deployment.
EXPLICIT CONSUMER POLICY · ILLUSTRATION
Is success preserved?
Require the selected subject and world, pinned Query/Claim/profile, four bindings, all nine obligations and accepted trust assumptions. Then inspect the established lifecycle comparison.
This illustration uses the recorded comparison for 70397233:5. Switching world views or exploring other transactions does not change that comparison. No live receipt is created and no application action is authorized.
Recorded-data policy illustration
In a live integration, consume the direct answer from an admitted SDK handle in the same authenticated context. A copied JSON result cannot substitute for that authority.
The exact historical input change
Target ; selected subject .
Encoded amount: → 0. Both derived Message.Data values contain 68 bytes.
The transaction, spender and every non-Data field were retained.
Inspect the exact bytes
RETAINED ACTUAL CONTROL
ORIGINAL A/B BRANCH EXECUTIONS, NOW RECORDED
The boundaries of this case.
A new, preselected Data-only request produced an alternate world and one verified lifecycle Claim in the bounded Chain 4663 domain.
Read the boundaries
“Approval” describes the input’s approve-shaped encoding. ERC-20 compliance, token balance or allowance proofs and the exact revert cause are not established.