pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,021,932
← previous block
next block →
recent activity
Analyzing
Block #96,021,932
12 transactions · 9 stateful · 2026-08-14 21:15:03 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,021,932
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
execOrders
#4
execPerpOps
#5
execPerpOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x94defb17
· blocks 1
#10
execFwdPositionOpsV2
#11
setData
#9
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xc2e8a8d0…07dc
0x968279…9342
4 touches
1 conflict
0xc2e8a8d0…07db
0x968279…9342
4 touches
1 conflict
0xc2e8a8d0…07da
0x968279…9342
4 touches
1 conflict
0xc2e8a8d0…07d7
0x968279…9342
4 touches
1 conflict
0xc2e8a8d0…07d6
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
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:
USDC (USDC)
1 conflict on slot
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity