pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,520,820
← previous block
next block →
recent activity
Analyzing
Block #96,520,820
9 transactions · 6 stateful · 2026-08-16 15:04:37 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,520,820
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#6
0x94defb17
· blocks 1
#8
setData
#5
execFwdPositionOpsV2
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a3ce287…6a5e
0x968279…9342
4 touches
1 conflict
0x125f0323…22c4
0x968279…9342
4 touches
1 conflict
0x125f0323…22c6
0x968279…9342
4 touches
1 conflict
0x7a3ce287…6a58
0x968279…9342
4 touches
1 conflict
0x7a3ce287…6a59
0x968279…9342
4 touches
1 conflict
0x7a3ce287…6a5c
0x968279…9342
4 touches
1 conflict
0x7a3ce287…6a5d
0x968279…9342
4 touches
1 conflict
0x3d93ad2c…e747
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:
0x96827978…f09342
1 conflict on slot
0x7a3ce287d3…b56a5e
Audit this contract →
← previous block
·
next block →
recent activity