← previous blocknext block →recent activity
Analyzing
Block #85,514,586
21 transactions · 17 stateful · 2026-07-04 09:09:30 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,514,586 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w19w011w212w113w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa435dee8…f2be
0x34b655…2a6f
8 touches
6 conflicts
0x12657c33…c88b
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x30faf03c…78b1
0x34b655…2a6f
4 touches
1 conflict
0x33e3dcdd…1f1f
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0xa435dee840…eef2be
Audit this contract →
← previous block·next block →recent activity