← previous blocknext block →recent activity
Analyzing
Block #85,133,416
26 transactions · 25 stateful · 2026-07-02 14:51:00 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,133,416 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w08w19w210w311w412w513w619w224w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x5b353877…605d
0x34b655…2a6f
12 touches
15 conflicts
0x264f7d7d…8444
0x34b655…2a6f
10 touches
10 conflicts
0x2b220e74…0724
0x34b655…2a6f
10 touches
10 conflicts
0x5407a954…a372
0x34b655…2a6f
10 touches
10 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x22e0cc1d…ad0d
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity