← previous blocknext block →recent activity
Analyzing
Block #83,627,858
18 transactions · 16 stateful · 2026-06-25 15:32:02 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,627,858 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w312w413w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
8 touches
6 conflicts
0xb6632320…a3ce
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x5df421ff…59da
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
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
6 conflicts on slot 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity