← sui7kNEFF…MxHHSucceededblock 0
Engine loading — 18 MB0 / 39
FetchingOpeningPositioning
move-disassembly
Narrow session: Code, Call Trace and Values only, read-only. The event log and stepping need a wider viewport.
  • CODE
The session is stopped at step 0 of 39

No source resolved for the code this transaction ran, so this recording is at instruction level: every step is a program counter into the contract's bytecode. A chain publishes the bytecode that ran and not the source it was built from, so source has to be obtained separately and proved against that bytecode — which has not happened for this contract. Stepping is complete either way.

Stepping continues at instruction level.

FunctionCallsSelf
<transaction>10
<toplevel>10
log_user_activity10
sender10
native_sender10
timestamp_ms10
emit10
By function — self cost, callees excluded.Call order
Frame
<transaction>
<toplevel>:327
log_user_activity:328
sender:15
native_sender:15
timestamp_ms:14
emit:389
By call order.Self cost

7 recorded entries — every call this recording opened, in the order it opened them, and 0 storage writes. Each row's step is its coordinate in the recording. The replay's reproduced effects are published as a count rather than one record each, so they are in the transaction pane and not in this timeline.

→call0<transaction>
→call0<toplevel>campaign.mvb:327
→call1log_user_activitycampaign.mvb:328
→call20sendertx_context.mvb:15
→call20native_sendertx_context.mvb:15
→call27timestamp_msclock.mvb:14
→call37emitcampaign.mvb:389
  • VALUES

This recording interns 10 variable name(s), and none of them is a program local: no debug symbols resolved for this contract, so what it names is the machine state this execution touched rather than anything from source. Their values travel in the container a live session reads, so this page can count them and not show them.