pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,506,334
← previous block
next block →
recent activity
Analyzing
Block #102,506,334
33 transactions · 27 stateful · 2026-09-06 15:37:59 UTC
Parallelism
76
/100
Blocked
52
%
Avg conflicts / tx
0.73
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,506,334
· 33 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0xa96df62f
#5
0x6a9d88db
#6
updatePrices
· blocks 1
#8
updatePrices
#9
updatePrices
#10
0xab083028
· blocks 2
#13
0x5acec890
#15
0x59558d29
#16
0x59558d29
#17
0x59558d29
#18
updateDataFeedsValuesPartial
#19
setData
#20
execFwdPositionOpsV2
· blocks 2
#23
execFwdPositionOpsV2
#24
updateTemporalNumericValuesV1
#29
0x6a9d88da
#30
execOrders
· blocks 2
#2
0x0c7abd22
· blocks 1
#7
updatePrices
#26
0xed82b078
· blocks 2
#31
execOrders
· blocks 1
#3
0x0c7abd22
· blocks 3
#27
0xed82b078
· blocks 1
#11
execOrders
· blocks 2
#14
0x5acec890
· blocks 2
#28
0xed82b078
#12
execOrders
· blocks 1
#32
execOrders
#21
execFwdPositionOpsV2
· blocks 1
#22
execFwdPositionOpsV2
· blocks 1
#25
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
7
w1
10
w0
11
w3
12
w4
14
w3
20
w0
21
w5
22
w6
25
w7
26
w1
27
w2
28
w3
30
w0
31
w1
32
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 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
0x0000000000…000012
Audit this contract →
← previous block
·
next block →
recent activity