pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,034,849
← previous block
next block →
recent activity
Analyzing
Block #96,034,849
11 transactions · 7 stateful · 2026-08-14 22:20:03 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,034,849
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
updatePriceFeedsIfNecessary
#5
0x3f5c179b
· blocks 1
#7
updateDataFeedsValuesPartial
#8
execOrders
#9
setData
#10
execOrders
#6
batchUpdate
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
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x003b6142…6bce
0x34b655…2a6f
2 touches
0 conflicts
0x0a255626…48e1
0x34b655…2a6f
2 touches
0 conflicts
0x1af644dc…0822
0x34b655…2a6f
2 touches
0 conflicts
0x28fa6e08…1bc6
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
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:
0x851145ea…9f3f07
1 conflict on slot
0x0705cc6c3d…b62c40
Audit this contract →
← previous block
·
next block →
recent activity