← previous blocknext block →recent activity
Analyzing
Block #85,351,904
55 transactions · 42 stateful · 2026-07-03 15:06:18 UTC
Parallelism
65/100
Blocked
79%
Avg conflicts / tx
3.16
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,351,904 · 55 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w111w213w314w415w543w644w645w746w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x3230277c…ef39
0xc8689a…ee79
14 touches
21 conflicts
0x5efa0d16…4a5d
0x34b655…2a6f
14 touches
21 conflicts
0xfefb0189…f726
0x34b655…2a6f
14 touches
21 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
12 touches
15 conflicts
0x5f34fd08…aeb3
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity