pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,191,250
← previous block
next block →
recent activity
Analyzing
Block #96,191,250
11 transactions · 8 stateful · 2026-08-15 11:26:43 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,191,250
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execPerpOps
#3
execPerpOps
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x29eed2d3
· blocks 1
#10
setData
#9
0x29eed2d3
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
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x9f9b9c01…4676
0x928dc8…8207
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x27f04eb4…d7ea
0x34b655…2a6f
2 touches
0 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
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