← previous blocknext block →recent activity
Analyzing
Block #85,250,004
14 transactions · 13 stateful · 2026-07-03 03:47:36 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,250,004 · 14 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
1w02w14w05w06w19w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cf2d0bf…8d46
0x34b655…2a6f
8 touches
6 conflicts
0x27f2c756…0ffc
0x34b655…2a6f
6 touches
3 conflicts
0xa4ef8c05…ceae
0x34b655…2a6f
4 touches
1 conflict
0x8483a2fc…b2f1
0x34b655…2a6f
4 touches
1 conflict
0x7ccc375a…26b0
0x34b655…2a6f
4 touches
1 conflict
0x6f64c012…6358
0x34b655…2a6f
4 touches
1 conflict
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
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 0x9cf2d0bf82…a78d46
Audit this contract →
← previous block·next block →recent activity