pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,659,338
← previous block
next block →
recent activity
Analyzing
Block #86,659,338
11 transactions · 7 stateful · 2026-07-09 16:31:26 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,659,338
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
forward
#5
approve
#6
0x448d20…342a
#7
0x376381…13c6
#8
setData
#9
exactInputSingle
#10
0x39435dac
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x94b46bd0…e95d
0x34b655…2a6f
4 touches
1 conflict
0x95c9704c…8a57
0x34b655…2a6f
4 touches
1 conflict
0x02fa570e…f8f2
0x34b655…2a6f
2 touches
0 conflicts
0x04e2320a…b3cf
0x34b655…2a6f
2 touches
0 conflicts
0x0c53719e…0366
0x34b655…2a6f
2 touches
0 conflicts
0x2833ba3e…8b1e
0x34b655…2a6f
2 touches
0 conflicts
0x2aba4f80…0d0d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x64aaadbf0a…79f9f3
Audit this contract →
← previous block
·
next block →
recent activity