The signing interface and the executed transaction told different stories. Start with the ownership event, then follow the record.
Radiant reported that compromised developer devices displayed benign transaction details while malicious payloads were signed. That off-chain explanation is separate from the public transaction record.
Radiant post-mortem, 18 October 2024 ↗Arbiscan shows a successful transaction in block 264,477,049 at 17:09:18 UTC. Its decoded OwnershipTransferred event is emitted by the Pool Provider, with the previous and new owners shown below.
Inspect the transaction and event log ↗The source-linked transaction containing the ownership event.
The event emitter identifies the contract whose ownership changed.
A historical event field, not a statement of present ownership.
The newOwner field in that event. An address is not a person’s identity.
Use the Arbitrum workspace link. Check the returned chain, receipt and source references. A new lookup may have less historical coverage than the explorer.
Compare the event emitter, previousOwner and newOwner. A successful receipt does not show that the signers intended the resulting authority change.
Follow each relevant transfer with its own transaction and amount. Do not treat a present-day balance, name tag or current token price as a historical loss calculation.