pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,798,072
← previous block
next block →
recent activity
Analyzing
Block #96,798,072
10 transactions · 10 stateful · 2026-08-17 14:19:05 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,798,072
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
relay
#2
execFwdPositionOpsV2
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
swapExactTokensForTokens
#9
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503d17fc…e0a9
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04f6d949…d859
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x2655625d…b058
0x34b655…2a6f
2 touches
0 conflicts
0x2840c278…bbc7
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
0x503d17fcf8…40e0a9
Audit this contract →
← previous block
·
next block →
recent activity