← previous blocknext block →recent activity
Analyzing
Block #86,486,402
83 transactions · 59 stateful · 2026-07-08 21:13:01 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
2
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,486,402 · 83 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w112w113w215w216w218w019w120w221w322w323w427w439w542w557w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x09497c1d…2305
0xd32edf…ff58
19 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
12 touches
15 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
10 touches
10 conflicts
0x7d2645cd…5d8e
0x34b655…2a6f
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity