pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,653,873
← previous block
next block →
recent activity
Analyzing
Block #96,653,873
12 transactions · 10 stateful · 2026-08-17 02:13:49 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,653,873
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updatePrices
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#10
setData
#11
swapExactTokensForTokens
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee50bd75…6ac3
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e89
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0x98834cc0…6c23
0x34b655…2a6f
4 touches
1 conflict
0x9d344866…9911
0x34b655…2a6f
4 touches
1 conflict
0xbcc2ea3e…8ea3
0x34b655…2a6f
4 touches
1 conflict
0xde55348a…f995
0x34b655…2a6f
4 touches
1 conflict
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
0xee50bd7555…676ac3
Audit this contract →
← previous block
·
next block →
recent activity