← previous blocknext block →recent activity
Analyzing
Block #85,803,314
18 transactions · 14 stateful · 2026-07-05 17:13:23 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,803,314 · 18 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
4w05w16w112w213w315w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9579025c…c3ec
0x34b655…2a6f
8 touches
6 conflicts
0x4d3e58e0…a2d7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0xef17b8cd…9511
0x34b655…2a6f
6 touches
3 conflicts
0x94f5fc74…a10d
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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 0x9579025c04…9ec3ec
Audit this contract →
← previous block·next block →recent activity