← previous blocknext block →recent activity
Analyzing
Block #83,623,361
31 transactions · 24 stateful · 2026-06-25 15:02:00 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,623,361 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w27w19w010w111w212w313w414w515w624w227w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 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: Perpl
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity