pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,059,413
← previous block
next block →
recent activity
Analyzing
Block #87,059,413
11 transactions · 8 stateful · 2026-07-11 13:04:37 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,059,413
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
redeemDelegations
#7
forward
#8
0x36f359b0
#9
setData
#10
exactInputSingle
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5decd02…dbf4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x194be77e…58ae
0x34b655…2a6f
2 touches
0 conflicts
0x1aef6331…1390
0x34b655…2a6f
2 touches
0 conflicts
0x2807ae1a…73b6
0x34b655…2a6f
2 touches
0 conflicts
0x3093e806…bde2
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
0xc5decd02b3…07dbf4
Audit this contract →
← previous block
·
next block →
recent activity