pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,654,007
← previous block
next block →
recent activity
Analyzing
Block #96,654,007
10 transactions · 10 stateful · 2026-08-17 02:14:30 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,654,007
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
updatePriceFeedsIfNecessary
#7
batchUpdate
#8
approve
#9
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3f1a31b5…9888
0x34b655…2a6f
2 touches
0 conflicts
0x5eac44da…0868
0x34b655…2a6f
2 touches
0 conflicts
0x9b36f19f…fa5a
0x34b655…2a6f
2 touches
0 conflicts
0xa03ccaf7…c77f
0x34b655…2a6f
2 touches
0 conflicts
0xab96ac84…a512
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
0x745952b2a0…a6d90c
Audit this contract →
← previous block
·
next block →
recent activity