← previous blocknext block →recent activity
Analyzing
Block #83,625,204
22 transactions · 19 stateful · 2026-06-25 15:14:17 UTC
Parallelism
73/100
Blocked
37%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,625,204 · 22 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
1w02w16w07w18w213w315w016w120w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3464910…786f
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x69df8a…6292
2 touches
0 conflicts
0xd8fd2add…50fc
0x69df8a…6292
2 touches
0 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
3 conflicts on slot 0xc346491067…b0786f
Audit this contract →
← previous block·next block →recent activity