pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,529,610
← previous block
next block →
recent activity
Analyzing
Block #97,529,610
11 transactions · 9 stateful · 2026-08-20 04:24:07 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,529,610
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketSell
#6
transfer
#7
setData
#8
0x59558d29
#9
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25d909da…1722
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x8f215609…e87e
0x065c9d…c394
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x00f505df…442a
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
0x25d909da6b…231722
Audit this contract →
← previous block
·
next block →
recent activity