pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,289,373
← previous block
next block →
recent activity
Analyzing
Block #96,289,373
11 transactions · 7 stateful · 2026-08-15 19:40:15 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,289,373
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5acec890
· blocks 1
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
forward
#9
setData
#10
0x61d59c2d
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d30a41e…7e0a
0x34b655…2a6f
2 touches
0 conflicts
0x3727225e…a3cf
0x34b655…2a6f
2 touches
0 conflicts
0x56c8d544…7898
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
0x34b655…2a6f
2 touches
0 conflicts
0x68297b76…8e24
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
0x733a5000e7…e16e67
Audit this contract →
← previous block
·
next block →
recent activity