← previous blocknext block →recent activity
Analyzing
Block #85,133,273
64 transactions · 56 stateful · 2026-07-02 14:50:03 UTC
Parallelism
70/100
Blocked
71%
Avg conflicts / tx
3.13
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,133,273 · 64 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
1w02w16w07w19w212w013w214w316w317w418w419w520w349w156w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0x9495bffc…46e6
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x25e3730b…24a9
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xc99e7125…81b1
0x34b655…2a6f
14 touches
21 conflicts
0xcbd788cd…1049
0x34b655…2a6f
12 touches
15 conflicts
0xd6418d68…bdc5
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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity