pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,383,219
← previous block
next block →
recent activity
Analyzing
Block #102,383,219
46 transactions · 46 stateful · 2026-09-06 05:14:01 UTC
Parallelism
93
/100
Blocked
7
%
Avg conflicts / tx
0.11
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,383,219
· 46 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x6a9cf69d
#3
updatePrices
#4
0xab083028
#5
execOrders
#6
0x59558d29
#7
execPerpOps
#8
0x0c7abd22
· blocks 2
#11
updateDataFeedsValuesPartial
#12
setData
#13
updatePriceFeedsIfNecessary
#14
CreateUser
#15
CreateMemory
#16
CreateUser
#17
CreateMemory
#18
CreateMemory
#19
CreateMemory
#20
CreateMemory
#21
CreateMemory
#22
CreateMemory
#23
CreateMemory
#24
CreateMemory
#25
CreateMemory
#26
CreateMemory
#27
CreateMemory
#28
CreateMemory
#29
CreateMemory
#30
CreateMemory
#31
CreateMemory
#32
CreateMemory
#33
CreateMemory
#34
CreateMemory
#35
CreateMemory
#36
CreateMemory
#37
CreateMemory
#38
CreateMemory
#39
CreateMemory
#40
CreateMemory
#41
CreateMemory
#42
execFwdPositionOpsV2
#43
0xed82b078
#44
execOrders
· blocks 1
#9
0x0c7abd22
· blocks 2
#10
0x0c7abd22
#45
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
10
w2
44
w0
45
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xf8480e2a…dff0
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x80a7269b…32ad
0xd32edf…ff58
5 touches
3 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.
The bottleneck
Throughput-killer:
ShMonad (shMON)
3 conflicts on slot
0xd9f18d9a4a…7f141d
Audit this contract →
← previous block
·
next block →
recent activity