← previous blocknext block →recent activity
Analyzing
Block #83,625,515
21 transactions · 20 stateful · 2026-06-25 15:16:21 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,625,515 · 21 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
1w02w15w06w17w28w39w410w512w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x7b72fd15…b096
0x34b655…2a6f
6 touches
3 conflicts
0xfaf22814…27c8
0x34b655…2a6f
6 touches
3 conflicts
0xe2263bea…6a9d
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6a9f
0x69df8a…6292
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity