pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,787,795
← previous block
next block →
recent activity
Analyzing
Block #86,787,795
12 transactions · 10 stateful · 2026-07-10 06:49:11 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,787,795
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x57368ddf
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#8
0x6a50965e
#9
setData
#10
0x09c420…81a6
#11
exactInputSingle
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8f2e700a…3175
0x34b655…2a6f
4 touches
1 conflict
0xbf863077…06c5
0x34b655…2a6f
4 touches
1 conflict
0xbf863077…06c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xce3cd522…e49d
0x34b655…2a6f
4 touches
1 conflict
0xe650955d…99f7
0x34b655…2a6f
4 touches
1 conflict
0x97c2aeb8…1710
0x34b655…2a6f
3 touches
1 conflict
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity