pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,186,141
← previous block
next block →
recent activity
Analyzing
Block #97,186,141
9 transactions · 8 stateful · 2026-08-18 23:03:57 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,186,141
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
#4
placeAndExecuteMarketSell
· blocks 2
#7
execOrders
#8
setData
#5
placeAndExecuteMarketSell
· blocks 1
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x520d22fe…11b7
0x851145…3f07
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
2 touches
0 conflicts
0x5eb187dd…b1d6
0x34b655…2a6f
2 touches
0 conflicts
0x876712ff…b058
0x34b655…2a6f
2 touches
0 conflicts
0xc5489df7…307d
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity