← previous blocknext block →recent activity
Analyzing
Block #86,625,138
74 transactions · 64 stateful · 2026-07-09 12:41:36 UTC
Parallelism
68/100
Blocked
80%
Avg conflicts / tx
3.49
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #86,625,138 · 74 txs across 24 waves · depth 24
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
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w515w217w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0xdebd443f…5a6a
0xd32edf…ff58
19 touches
45 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0x04fdea…47d7
14 touches
21 conflicts
0x5fad6fee…7714
0x34b655…2a6f
12 touches
15 conflicts
0x3230277c…ef39
0xc8689a…ee79
12 touches
15 conflicts
0x02991b41…19e6
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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity