pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,714,130
← previous block
next block →
recent activity
Analyzing
Block #95,714,130
11 transactions · 11 stateful · 2026-08-13 19:26:21 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,714,130
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOpsV2
#3
0x3f5c179b
#4
execFwdPositionOpsV2
#5
0x94defb17
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a7e1ad4
#10
setData
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x958ba9d3…700b
0x968279…9342
4 touches
1 conflict
0x958ba9d3…700e
0x968279…9342
4 touches
1 conflict
0x958ba9d3…700f
0x968279…9342
4 touches
1 conflict
0x958ba9d3…7011
0x968279…9342
4 touches
1 conflict
0xe9be6d71…c9bf
0x968279…9342
4 touches
1 conflict
0xe9be6d71…c9c0
0x968279…9342
4 touches
1 conflict
0xe9be6d71…c9c2
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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
0x958ba9d360…28700b
Audit this contract →
← previous block
·
next block →
recent activity