pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,661,148
← previous block
next block →
recent activity
Analyzing
Block #87,661,148
10 transactions · 8 stateful · 2026-07-14 08:09:13 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
#87,661,148
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0xbf82f22b
#8
setData
#9
0x61633731
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf47128a0…896a
0x34b655…2a6f
4 touches
1 conflict
0xe648d72f…b26c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e07
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e08
0x34b655…2a6f
4 touches
1 conflict
0x33da0dfa…bac6
0x34b655…2a6f
4 touches
1 conflict
0x3e1b21c6…b1e4
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
0xf47128a08a…5c896a
Audit this contract →
← previous block
·
next block →
recent activity