← previous blocknext block →recent activity
Analyzing
Block #83,661,538
24 transactions · 23 stateful · 2026-06-25 19:16:50 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,661,538 · 24 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
3w04w05w16w07w18w19w210w311w412w521w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa50fcb98…2b01
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x85b992ec…db0e
0x34b655…2a6f
7 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x478e6e08…83bf
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdf37a93d…879b
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
28 conflicts on slot 0xa50fcb98bd…342b01
Audit this contract →
← previous block·next block →recent activity