pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,374,323
← previous block
next block →
recent activity
Analyzing
Block #96,374,323
10 transactions · 9 stateful · 2026-08-16 02:47:31 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,374,323
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0xa96df62f
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#6
executeBatch
#7
execFwdPositionOpsV2
#9
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xfea142d7…d423
0x0a3323…0a3c
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 conflicts
0x63f5c02f…6853
0x3bd359…433a
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity