← previous blocknext block →recent activity
Analyzing
Block #83,628,109
17 transactions · 14 stateful · 2026-06-25 15:33:43 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,628,109 · 17 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
4w05w17w08w09w111w212w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2ab3ad1…a6bc
0x34b655…2a6f
6 touches
3 conflicts
0x3ed61588…0c31
0x34b655…2a6f
4 touches
1 conflict
0x6b2a6570…0e70
0x34b655…2a6f
4 touches
1 conflict
0x71dfad7e…5c10
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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
3 conflicts on slot 0xc2ab3ad132…8da6bc
Audit this contract →
← previous block·next block →recent activity