pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,435,136
← previous block
next block →
recent activity
Analyzing
Block #96,435,136
11 transactions · 8 stateful · 2026-08-16 07:53:20 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,435,136
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
· blocks 1
#3
0x94defb17
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
deposit
#9
transfer
#10
setData
#4
0x94defb17
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x781e848d…fc4c
0x968279…9342
4 touches
1 conflict
0x4d3495aa…7ce1
0x968279…9342
4 touches
1 conflict
0x4d3495aa…7ce2
0x968279…9342
4 touches
1 conflict
0x4d3495aa…7ce5
0x968279…9342
4 touches
1 conflict
0x4d3495aa…7ce6
0x968279…9342
4 touches
1 conflict
0x4d3495aa…7ce8
0x968279…9342
4 touches
1 conflict
0x781e848d…fc49
0x968279…9342
4 touches
1 conflict
0x781e848d…fc4a
0x968279…9342
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
0x781e848d5c…0efc4c
Audit this contract →
← previous block
·
next block →
recent activity