← previous blocknext block →recent activity
Analyzing
Block #83,627,773
18 transactions · 17 stateful · 2026-06-25 15:31:28 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,627,773 · 18 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
3w04w05w06w19w110w212w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90fefe5e…f0c6
0x34b655…2a6f
6 touches
3 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
6 touches
3 conflicts
0x13aceb70…cf9f
0x34b655…2a6f
6 touches
3 conflicts
0x7534f53d…6ed4
0x34b655…2a6f
4 touches
1 conflict
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0x909c2852…f823
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 0x90fefe5e59…bbf0c6
Audit this contract →
← previous block·next block →recent activity