← previous blocknext block →recent activity
Analyzing
Block #85,125,331
41 transactions · 38 stateful · 2026-07-02 13:56:56 UTC
Parallelism
73/100
Blocked
71%
Avg conflicts / tx
2.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,125,331 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w29w310w411w512w630w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x0e5f2a94…4732
0x34b655…2a6f
12 touches
15 conflicts
0xd16df6cd…5532
0x40c49f…2af0
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0xf5310ef7…485a
0x40c49f…2af0
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity