pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,086,529
← previous block
next block →
recent activity
Analyzing
Block #96,086,529
13 transactions · 11 stateful · 2026-08-15 02:39:58 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,086,529
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc9623387
#2
0x3f5c179b
#3
execFwdPositionOpsV2
· blocks 1
#4
execOrders
#5
execFwdPositionOpsV2
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
transfer
· blocks 1
#12
setData
#6
execFwdPositionOpsV2
#11
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0x97288dcc…09d7
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
2 touches
0 conflicts
0x0705cc6c…2c40
0x851145…3f07
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
0x981b7617b5…896093
Audit this contract →
← previous block
·
next block →
recent activity