← previous blocknext block →recent activity
Analyzing
Block #85,162,947
15 transactions · 15 stateful · 2026-07-02 18:07:43 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,162,947 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w08w19w110w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
10 touches
10 conflicts
0x2406ccf7…c1cb
0x34b655…2a6f
6 touches
3 conflicts
0xebc52107…becf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x765cd07a…1018
0x34b655…2a6f
4 touches
1 conflict
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x05b1b07a…7a99
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
10 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity