← previous blocknext block →recent activity
Analyzing
Block #85,916,607
12 transactions · 9 stateful · 2026-07-06 05:47:59 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,916,607 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1d3dac50…4731
0x34b655…2a6f
4 touches
1 conflict
0x8ec76616…6cb3
0x0c65a0…0852
2 touches
0 conflicts
0x03ce88d7…ea0d
0x34b655…2a6f
2 touches
0 conflicts
0x23165113…5d82
0x34b655…2a6f
2 touches
0 conflicts
0x30323797…a638
0x34b655…2a6f
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity