← previous blocknext block →recent activity
Analyzing
Block #83,636,697
24 transactions · 23 stateful · 2026-06-25 16:31:07 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,636,697 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w28w119w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c320a0…b4a8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x369a11e2…566f
0x34b655…2a6f
6 touches
3 conflicts
0x36c9b0ab…5c95
0x34b655…2a6f
4 touches
1 conflict
0x39f7e392…23ee
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
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 0x99c320a0a0…feb4a8
Audit this contract →
← previous block·next block →recent activity