pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,382,420
← previous block
next block →
recent activity
Analyzing
Block #106,382,420
17 transactions · 15 stateful · 2026-09-20 05:41:42 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
#106,382,420
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
#5
0x5acec890
#6
0x59558d29
#7
0x59558d29
#8
execPerpOps
#9
execPerpOps
#10
execOrders
#11
updateDataFeedsValuesPartial
#12
setData
#13
execFwdPositionOpsV2
#14
transfer
#15
0x6aaf721a
#16
execOrders
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
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x32cdd30c…4e04
0x34b655…2a6f
2 touches
0 conflicts
0x3786a2d7…4c21
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
2 touches
0 conflicts
0x516f0cd2…ea0b
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