pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,356,077
← previous block
next block →
recent activity
Analyzing
Block #96,356,077
11 transactions · 7 stateful · 2026-08-16 01:15:44 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,356,077
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
execOrders
#5
0xa96df62f
#6
execPerpOps
#7
execPerpOps
#8
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x67459137…de7e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x3a874ce6…22d1
0x34b655…2a6f
2 touches
0 conflicts
0x5df7cf2b…bbe5
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:
Perpl
1 conflict on slot
0x3c0e49c972…657833
Audit this contract →
← previous block
·
next block →
recent activity