← previous blocknext block →recent activity
Analyzing
Block #85,103,709
25 transactions · 18 stateful · 2026-07-02 11:32:07 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,103,709 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w212w313w421w522w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x7fa1794c…3323
0x34b655…2a6f
4 touches
1 conflict
0xb05d58cd…a43d
0x34b655…2a6f
4 touches
1 conflict
0xcbd788cd…1049
0x34b655…2a6f
4 touches
1 conflict
0x3230277c…ef39
0xc8689a…ee79
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity