pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,181,101
← previous block
next block →
recent activity
Analyzing
Block #96,181,101
13 transactions · 11 stateful · 2026-08-15 10:35:41 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,181,101
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
setData
#5
execFwdPositionOpsV2
#6
0x61d59c2d
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b1a9431…183e
0x34b655…2a6f
2 touches
0 conflicts
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x3028debf…a3b4
0x34b655…2a6f
2 touches
0 conflicts
0x364026a6…1715
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
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.
← previous block
·
next block →
recent activity