← solana-mainnet43hUoc…Y6exSucceededblock 459262601
Engine loading — 18 MB0 / 26
FetchingOpeningPositioning
sbf-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 26

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
transaction 43hUocSFvzK4JNus5LEVjMgBVt2DD15fVFjxumLb6v3VSncftpk4raczgKAmnxCpLaagdbu1ftG9eXpxQd49Y6ex10
instruction 0 → dijkbkCAKfFTCxQg3u1pg82gVU1jJGHBBRcteD11mBu10
By function — self cost, callees excluded.Call order
Frame
<transaction>
<toplevel>:1
transaction 43hUocSFvzK4JNus5LEVjMgBVt2DD15fVFjxumLb6v3VSncftpk4raczgKAmnxCpLaagdbu1ftG9eXpxQd49Y6ex:1
instruction 0 → dijkbkCAKfFTCxQg3u1pg82gVU1jJGHBBRcteD11mBu:2
By call order.Self cost

4 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>transaction.txt:1
→call1transaction 43hUocSFvzK4JNus5LEVjMgBVt2DD15fVFjxumLb6v3VSncftpk4raczgKAmnxCpLaagdbu1ftG9eXpxQd49Y6extransaction.txt:1
→call2instruction 0 → dijkbkCAKfFTCxQg3u1pg82gVU1jJGHBBRcteD11mBudijkbkCAKfFTCxQg3u1pg82gVU1jJGHBBRcteD11mBu-74f70ea7bf98259d.sbf:2
  • VALUES

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