pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,197,862
← previous block
next block →
recent activity
Analyzing
Block #97,197,862
9 transactions · 7 stateful · 2026-08-19 00:03:05 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,197,862
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
matchOrders
#3
updateDataFeedsValuesPartial
#4
updatePriceFeedsIfNecessary
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d0bf98a…b467
0x34b655…2a6f
4 touches
1 conflict
0xe9662735…4f99
0x34b655…2a6f
4 touches
1 conflict
0xec51360c…c30b
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4065
0x34b655…2a6f
4 touches
1 conflict
0xe9e92bac…00ed
0x754704…b603
2 touches
0 conflicts
0x68c08dd2…be14
0x99c7a7…8bf0
2 touches
0 conflicts
0xdfac3ce0…6699
0x99c7a7…8bf0
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
0x8d0bf98a07…cbb467
Audit this contract →
← previous block
·
next block →
recent activity