Skip to content
FORENSIAWeb3 forensicsOpen workspace
FORENSIAOpen workspace
Menu
← The field guide
Execution / Illustrated lesson

Reentrancy
An external call can come back before the first finishes.

A contract that calls another contract may give it an opportunity to call back. If the first contract’s accounting is not protected appropriately, repeated entry can violate its intended rules.

Reading history stays in this browser. Manage it in My Explore.
  1. 01

    A contract makes an external call

  2. 02

    The recipient calls back

  3. 03

    The first operation has not finished

Illustrative sequence. This diagram is a teaching aid, not a captured transaction.

What to collect

  1. Nested call order and callers
  2. Relevant code and state updates
  3. Surviving balance changes
Before drawing a conclusion

Repeated calls are not enough to establish reentrancy. The nested order and vulnerable state handling must support the explanation.

Test the idea

A function runs twice in one transaction. Is that automatically reentrancy?

Reveal the explanation

No. Sequential calls are different from nested re-entry. Examine the call tree and the contract’s state handling.

Try a practice scenario ↗