← sui9MySvi…h42hSucceededblock 0
Engine loading — 18 MB0 / 115
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 115

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
settlement_prologue10
sender20
native_sender20
record_settlement_sui_conservation10
settle_u12810
accumulator_key10
root_has_accumulator10
exists_with_type10
uid_to_address20
hash_type_and_key20
has_child_object_with_ty10
root_borrow_accumulator_mut10
borrow_mut10
borrow_child_object_mut10
update_u12810
is_zero_u12810
By function — self cost, callees excluded.Call order
Frame
<transaction>
<toplevel>:17
settlement_prologue:18
sender:15
native_sender:15
record_settlement_sui_conservation:30
settle_u128:39
sender:15
native_sender:15
accumulator_key:115
root_has_accumulator:134
exists_with_type:165
uid_to_address:189
hash_type_and_key:170
has_child_object_with_ty:174
root_borrow_accumulator_mut:153
borrow_mut:67
uid_to_address:189
hash_type_and_key:71
borrow_child_object_mut:75
update_u128:90
is_zero_u128:105
By call order.Self cost

22 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>accumulator_settlement.mvb:17
→call1settlement_prologueaccumulator_settlement.mvb:18
→call2sendertx_context.mvb:15
→call2native_sendertx_context.mvb:15
→call10record_settlement_sui_conservationaccumulator_settlement.mvb:30
→call12settle_u128accumulator_settlement.mvb:39
→call14sendertx_context.mvb:15
→call14native_sendertx_context.mvb:15
→call31accumulator_keyaccumulator.mvb:115
→call39root_has_accumulatoraccumulator.mvb:134
→call43exists_with_typedynamic_field.mvb:165
→call45uid_to_addressobject.mvb:189
→call53hash_type_and_keydynamic_field.mvb:170
→call57has_child_object_with_tydynamic_field.mvb:174
→call64root_borrow_accumulator_mutaccumulator.mvb:153
→call68borrow_mutdynamic_field.mvb:67
→call71uid_to_addressobject.mvb:189
→call77hash_type_and_keydynamic_field.mvb:71
→call81borrow_child_object_mutdynamic_field.mvb:75
→call90update_u128accumulator.mvb:90
→call104is_zero_u128accumulator.mvb:105
  • VALUES

This recording interns 13 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.