← previous blocknext block →recent activity
Analyzing
Block #86,625,762
43 transactions · 38 stateful · 2026-07-09 12:45:46 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.26
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,625,762 · 43 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w19w212w013w114w215w316w417w518w619w720w821w922w325w228w135w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
10 touches
10 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
6 touches
3 conflicts
0x37d710c8…45c1
0x34b655…2a6f
6 touches
3 conflicts
0x3b1ac26f…70c6
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity