← previous blocknext block →recent activity
Analyzing
Block #86,625,722
83 transactions · 62 stateful · 2026-07-09 12:45:30 UTC
Parallelism
76/100
Blocked
74%
Avg conflicts / tx
2.94
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,625,722 · 83 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w011w113w118w319w421w522w624w725w869w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
18 touches
36 conflicts
0x996d5951…b1f0
0xd32edf…ff58
17 touches
36 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
16 touches
28 conflicts
0x258fcaf5…2084
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x0f8965bb…e238
0x34b655…2a6f
16 touches
28 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity