← previous blocknext block →recent activity
Analyzing
Block #86,678,551
65 transactions · 54 stateful · 2026-07-09 18:39:37 UTC
Parallelism
65/100
Blocked
80%
Avg conflicts / tx
3.55
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #86,678,551 · 65 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w17w08w110w212w321w222w346w248w349w451w552w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…00c9
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x427d1120…4eb1
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…642d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…641f
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity