pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,784,749
← previous block
next block →
recent activity
Analyzing
Block #96,784,749
10 transactions · 9 stateful · 2026-08-17 13:12:04 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,784,749
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x9e76c652
#8
setData
#9
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x514ce6c4…39e5
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x5c21fdf2…29c7
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
2 touches
0 conflicts
0x0d256437…ceb8
0x34b655…2a6f
2 touches
0 conflicts
0x1a0baea4…49df
0x34b655…2a6f
2 touches
0 conflicts
0x1ce53ff5…e207
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
0x261cbea79d…12e35e
Audit this contract →
← previous block
·
next block →
recent activity