pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,320,137
← previous block
next block →
recent activity
Analyzing
Block #87,320,137
13 transactions · 12 stateful · 2026-07-12 18:08:02 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,320,137
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updatePrices
#4
execFwdPositionOps
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#9
relay
#10
setData
#11
approve
#12
0xc7e3ec2c
#2
swap
#7
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9f83113a…dcd8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0fff0643…9a0d
0x47464d…7777
2 touches
1 conflict
0x2b679442…d704
0x47464d…7777
2 touches
0 conflicts
0x67d846dd…358c
0x47464d…7777
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
0x39cc218566…27caca
Audit this contract →
← previous block
·
next block →
recent activity