← previous blocknext block →recent activity
Analyzing
Block #86,673,730
60 transactions · 48 stateful · 2026-07-09 18:07:28 UTC
Parallelism
67/100
Blocked
79%
Avg conflicts / tx
3.22
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,673,730 · 60 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
1w02w13w24w25w38w19w210w411w312w413w517w318w619w724w625w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xcbd788cd…1049
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
16 touches
28 conflicts
0xe4af4c87…9964
0x34b655…2a6f
14 touches
21 conflicts
0xb1a2ac22…f6de
0x34b655…2a6f
14 touches
21 conflicts
0xd87989c3…ad0d
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity