pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#117,305,531
← previous block
next block →
recent activity
Analyzing
Block #117,305,531
17 transactions · 16 stateful · 2026-10-28 10:44:01 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
#117,305,531
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x59558d29
#2
updatePrices
#3
0x35e534ea
#4
0x35e534ea
#5
0x35e534ea
#6
0x35e534ea
#7
execOrders
#8
0xa96df62f
#9
0x5acec890
#10
0x5acec890
#11
0x5acec890
#12
execFwdPositionOpsV2
#13
execFwdPositionOpsV2
#14
execFwdPositionOpsV2
#15
0x57368ddf
#16
setData
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
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x1aacaa39…9fdb
0x264123…670e
2 touches
0 conflicts
0x2489853d…60a2
0x264123…670e
2 touches
0 conflicts
0x27fc0b93…80ad
0x264123…670e
2 touches
0 conflicts
0x33ef7909…fc8e
0x264123…670e
2 touches
0 conflicts
0x666889a7…968f
0x264123…670e
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