pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,603,799
← previous block
next block →
recent activity
Analyzing
Block #96,603,799
10 transactions · 9 stateful · 2026-08-16 22:01:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,603,799
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
withdraw
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x97862f28…4ede
0x34b655…2a6f
4 touches
1 conflict
0xb46bb9bf…deb7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x177f744d…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x575a11d2…e67a
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
0x42b10c5765…853ee7
Audit this contract →
← previous block
·
next block →
recent activity