← previous blocknext block →recent activity
Analyzing
Block #83,617,339
27 transactions · 20 stateful · 2026-06-25 14:21:43 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,617,339 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w09w010w111w212w313w425w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
8 touches
6 conflicts
0x13aceb70…cf9f
0x34b655…2a6f
7 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x91e0bb94…ef45
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity