← previous blocknext block →recent activity
Analyzing
Block #85,496,695
52 transactions · 39 stateful · 2026-07-04 07:10:32 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #85,496,695 · 52 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w19w110w212w324w025w126w227w328w429w530w631w736w237w338w839w341w442w443w248w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xcf827da3…f2a5
0x34b655…2a6f
12 touches
15 conflicts
0xa435dee8…f2be
0x34b655…2a6f
10 touches
13 conflicts
0x459573ed…fbbe
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity