← previous blocknext block →recent activity
Analyzing
Block #83,410,534
17 transactions · 13 stateful · 2026-06-24 15:21:41 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,410,534 · 17 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
6w07w18w29w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
8 touches
6 conflicts
0x0835adb5…ad83
0x34b655…2a6f
8 touches
6 conflicts
0xf23ae251…22ff
0x34b655…2a6f
6 touches
3 conflicts
0x758bd24b…cc0c
0x34b655…2a6f
6 touches
3 conflicts
0x4ed3af20…d87d
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity