← previous blocknext block →recent activity
Analyzing
Block #85,706,634
11 transactions · 10 stateful · 2026-07-05 06:29:41 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,706,634 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3793dc52…110c
0x34b655…2a6f
4 touches
1 conflict
0x505d32fe…14ad
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xaf41644f…8f2e
0x0c65a0…0852
2 touches
0 conflicts
0xdbb3421b…b45b
0x0c65a0…0852
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x373f94db…c177
0x3bd359…433a
2 touches
0 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
1 conflict on slot 0x3793dc5298…b5110c
Audit this contract →
← previous block·next block →recent activity