pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,672,237
← previous block
next block →
recent activity
Analyzing
Block #97,672,237
10 transactions · 10 stateful · 2026-08-20 16:31:25 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,672,237
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x61d59c2d
#8
0x59558d29
#9
modifyLiquidities
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x14062aed…6e43
0x34b655…2a6f
2 touches
0 conflicts
0x3f4f9f22…8ad7
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x5fe6fd66…b220
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
0x574628e919…e4dcc3
Audit this contract →
← previous block
·
next block →
recent activity