← previous blocknext block →recent activity
Analyzing
Block #85,172,119
13 transactions · 9 stateful · 2026-07-02 19:08:43 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,172,119 · 13 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
7w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c8bf18d…c8f8
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x12c6929d…e7db
0x34b655…2a6f
2 touches
0 conflicts
0x1b1451d3…e1f4
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x4bfbf321…d4f2
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 0x6c8bf18de7…e3c8f8
Audit this contract →
← previous block·next block →recent activity