← previous blocknext block →recent activity
Analyzing
Block #85,353,311
68 transactions · 52 stateful · 2026-07-03 15:15:42 UTC
Parallelism
72/100
Blocked
81%
Avg conflicts / tx
3.24
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,353,311 · 68 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
1w02w13w24w35w46w57w68w79w810w916w319w428w1434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x8071538a…5b3f
0xd32edf…ff58
21 touches
55 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0xc6a8c250…737e
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x1da60af2…3010
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity