← previous blocknext block →recent activity
Analyzing
Block #83,410,034
17 transactions · 15 stateful · 2026-06-24 15:18:20 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,410,034 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w011w013w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x708619a6…d52a
0x34b655…2a6f
4 touches
1 conflict
0x758bd24b…cc0c
0x34b655…2a6f
4 touches
1 conflict
0xb6632320…a3ce
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdb19247d…233c
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity