pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,602,089
← previous block
next block →
recent activity
Analyzing
Block #92,602,089
19 transactions · 18 stateful · 2026-08-02 21:59:01 UTC
Parallelism
95
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,602,089
· 19 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
CreateMemory
#4
CreateMemory
#5
CreateMemory
#6
CreateMemory
#7
CreateMemory
#8
CreateMemory
#9
CreateMemory
#10
CreateMemory
#11
CreateMemory
#12
execFwdPositionOps
#13
execFwdPositionOps
#14
updateDataFeedsValuesPartial
#15
updateDataFeedsValuesPartial
#16
setData
#17
execOrders
#18
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
0x168f7615…a8de
0x34b655…2a6f
2 touches
0 conflicts
0x2a706fd8…de7e
0x34b655…2a6f
2 touches
0 conflicts
0x388b63a9…5008
0x34b655…2a6f
2 touches
0 conflicts
0x4135632d…613b
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