pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,447,525
← previous block
next block →
recent activity
Analyzing
Block #96,447,525
11 transactions · 10 stateful · 2026-08-16 08:55:39 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,447,525
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#5
swap
#6
0x94defb17
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#10
withdraw
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x0313aedc…bfaf
0x34b655…2a6f
2 touches
0 conflicts
0x0313aedc…bfb0
0x34b655…2a6f
2 touches
0 conflicts
0x0c970d6e…72c6
0x34b655…2a6f
2 touches
0 conflicts
0x0cc65720…396c
0x34b655…2a6f
2 touches
0 conflicts
0x0d488000…3831
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
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity