← previous blocknext block →recent activity
Analyzing
Block #85,104,654
40 transactions · 32 stateful · 2026-07-02 11:38:38 UTC
Parallelism
63/100
Blocked
81%
Avg conflicts / tx
2.35
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,104,654 · 40 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w210w313w014w115w217w018w119w220w321w422w523w624w729w430w331w132w233w534w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x10f55eea…0090
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x307414a5…7214
0x34b655…2a6f
8 touches
6 conflicts
0x43ffd8bd…0d0c
0x34b655…2a6f
8 touches
6 conflicts
0x51a914cf…a822
0x34b655…2a6f
8 touches
6 conflicts
0x65bb8d8c…8bb0
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity