← previous blocknext block →recent activity
Analyzing
Block #85,514,335
9 transactions · 7 stateful · 2026-07-04 09:07:50 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,514,335 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe86e36d3…d737
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x12657c33…c88b
0x34b655…2a6f
2 touches
0 conflicts
0x213a54fa…c85f
0x34b655…2a6f
2 touches
0 conflicts
0x33e3dcdd…1f1f
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 0x05edf2cf71…d3ac3c
Audit this contract →
← previous block·next block →recent activity