pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,466,345
← previous block
next block →
recent activity
Analyzing
Block #97,466,345
14 transactions · 11 stateful · 2026-08-19 23:05:36 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,466,345
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
execOrder
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
0x3f5c179b
#8
0x3f5c179b
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
batchUpdatePrice
#12
setData
#13
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x25d909da…1722
0x34b655…2a6f
2 touches
0 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
2 touches
0 conflicts
0x351f4dd5…7d10
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.
← previous block
·
next block →
recent activity