← previous blocknext block →recent activity
Analyzing
Block #85,138,599
22 transactions · 18 stateful · 2026-07-02 15:25:34 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,138,599 · 22 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
1w02w13w26w010w111w212w313w414w516w218w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x366f651e…6100
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x6ca32a09…4e48
0x34b655…2a6f
6 touches
3 conflicts
0xe31fbb3b…42d5
0x34b655…2a6f
6 touches
3 conflicts
0x5ab1d302…9100
0x34b655…2a6f
4 touches
1 conflict
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0x7c63ea28…e8af
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity