pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,786,865
← previous block
next block →
recent activity
Analyzing
Block #96,786,865
11 transactions · 10 stateful · 2026-08-17 13:22:43 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,786,865
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
claimRewards
#5
0x3f5c179b
· blocks 1
#7
placeBet
· blocks 1
#9
0x57368ddf
#10
setData
#6
batchUpdate
#8
placeBet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0xdf93c009…d51f
0x851145…3f07
4 touches
1 conflict
0x151b88cc…996c
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x2618f658…759a
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity