← previous blocknext block →recent activity
Analyzing
Block #106,155,121
19 transactions · 19 stateful · 2026-09-19 10:37:44 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,155,121 · 19 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
3w05w16w29w010w111w212w313w414w015w116w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3b4402…74e6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x675fa4ed…02bf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xb137d1de…c001
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0xaa3b44023d…a974e6
Audit this contract →
← previous block·next block →recent activity