← previous blocknext block →recent activity
Analyzing
Block #83,622,320
24 transactions · 23 stateful · 2026-06-25 14:55:03 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,622,320 · 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
7w08w19w210w311w412w513w617w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
14 touches
21 conflicts
0xacb576ad…e0a1
0x34b655…2a6f
10 touches
10 conflicts
0x2e86dd1e…dc3e
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xedc03135…d01b
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity