← previous blocknext block →recent activity
Analyzing
Block #106,342,226
16 transactions · 16 stateful · 2026-09-20 02:19:24 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,342,226 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w19w010w111w212w313w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x083ad52c…cd8f
0x6f6493…b480
9 touches
10 conflicts
0x0c0d7f16…0097
0x6f6493…b480
9 touches
10 conflicts
0x0c4a16b5…daba
0x6f6493…b480
9 touches
10 conflicts
0x0dc26665…8b5c
0x6f6493…b480
9 touches
10 conflicts
0x218b928f…c934
0x6f6493…b480
9 touches
10 conflicts
0x3012cf98…fd42
0x6f6493…b480
9 touches
10 conflicts
0x35f3aed1…6a75
0x6f6493…b480
9 touches
10 conflicts
0x37f677ec…b175
0x6f6493…b480
9 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x6f6493e3…08b480
10 conflicts on slot 0x083ad52c81…00cd8f
Audit this contract →
← previous block·next block →recent activity