pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,928,457
← previous block
next block →
recent activity
Analyzing
Block #86,928,457
10 transactions · 8 stateful · 2026-07-10 22:29:35 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,928,457
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
0x57368ddf
#7
execFwdPositionOps
#8
0x6a5172c7
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf60062ab…f98d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x489646ad…1521
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0xa5ec4b99…598f
0x34b655…2a6f
4 touches
1 conflict
0xbe688f2c…2f2e
0x34b655…2a6f
4 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
0xf60062ab4e…aef98d
Audit this contract →
← previous block
·
next block →
recent activity