pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,246,003
← previous block
next block →
recent activity
Analyzing
Block #92,246,003
16 transactions · 14 stateful · 2026-08-01 16:08:08 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,246,003
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0xab083028
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
redeemDelegations
#9
execFwdPositionOps
#10
executeBatch
#11
0x6a6e1a60
#12
setData
#13
execOrders
#14
execOrders
#15
updatePrices
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x50e84e6c…287f
0x34b655…2a6f
2 touches
0 conflicts
0x6323c5ea…ce8a
0x34b655…2a6f
2 touches
0 conflicts
0x735393b0…1e98
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