← previous blocknext block →recent activity
Analyzing
Block #85,182,246
44 transactions · 37 stateful · 2026-07-02 20:16:17 UTC
Parallelism
61/100
Blocked
78%
Avg conflicts / tx
2.82
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,182,246 · 44 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w07w29w212w313w014w115w216w317w118w019w120w221w322w423w524w625w735w236w438w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x833ebd97…5abb
0x34b655…2a6f
12 touches
15 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
12 touches
15 conflicts
0x30153288…6d46
0x34b655…2a6f
12 touches
15 conflicts
0x3230277c…ef39
0xc8689a…ee79
12 touches
15 conflicts
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x58603063…4ef0
0x34b655…2a6f
12 touches
15 conflicts
0xd29e547b…a1dd
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity