← previous blocknext block →recent activity
Analyzing
Block #83,633,108
23 transactions · 18 stateful · 2026-06-25 16:07:07 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,633,108 · 23 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
3w04w110w011w112w213w314w418w419w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x1d4b0baf…1423
0x34b655…2a6f
9 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x4abf223d…0915
0x34b655…2a6f
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x1b925784…660d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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