← previous blocknext block →recent activity
Analyzing
Block #83,625,180
19 transactions · 14 stateful · 2026-06-25 15:14:08 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,625,180 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w011w112w213w315w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xff107718…55e9
0x34b655…2a6f
4 touches
2 conflicts
0x126a0344…4465
0x34b655…2a6f
4 touches
1 conflict
0x46b23718…762f
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity