pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,204,914
← previous block
next block →
recent activity
Analyzing
Block #102,204,914
80 transactions · 53 stateful · 2026-09-05 14:10:40 UTC
Parallelism
91
/100
Blocked
42
%
Avg conflicts / tx
0.65
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,204,914
· 80 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0xd524a9da
#4
0xd524a9da
· blocks 4
#5
0xa4f52c…d591
#7
executePacked
· blocks 2
#8
0x1ada0a83
#9
createModule
#10
approve
#11
swap
#13
0x6a9c22e2
· blocks 1
#16
0xab083028
#17
0xab083028
#19
updatePrices
#20
updatePrices
#21
updatePrices
#22
updatePrices
#23
updatePrices
#24
0x50a0b275
#25
swap
· blocks 1
#27
execute
#29
0x6a9c22e2
#30
0x4f819052
#31
0x5acec890
· blocks 4
#32
0x0c7abd22
· blocks 3
#35
updateDataFeedsValuesPartial
#36
0xab083028
#37
execOrders
#38
0x7ef2e478
#39
0x5acec890
#40
0x5acec890
#41
0x5acec890
#42
0x4cb2db39
· blocks 1
#44
0x59558d29
#45
0x59558d29
#46
execPerpOps
#47
execPerpOps
#48
0xe3a3c9cc
#50
0x41a8f47c
#51
setData
· blocks 1
#53
execFwdPositionOpsV2
#54
execFwdPositionOpsV2
#55
execFwdPositionOpsV2
· blocks 2
#56
0x62be7533
#57
0x62be7533
#63
0x6a9c22e2
#65
approve
#66
execOrders
#67
execOrders
#68
execOrders
#69
execOrders
#70
execOrders
#72
execOrders
#73
execOrders
#74
execOrders
· blocks 2
#77
execOrders
#79
execOrders
#6
0xaf5e395a
· blocks 3
#12
executePacked
· blocks 1
#26
swap
#33
0x0c7abd22
· blocks 2
#43
0x59558d29
#52
setData
#58
execFwdPositionOpsV2
· blocks 5
#64
0x6a9c22e2
#14
executePacked
#15
0xab083028
· blocks 6
#34
0x0c7abd22
· blocks 1
#60
execFwdPositionOpsV2
#71
execOrders
· blocks 3
#18
0xab083028
· blocks 3
#28
main_all
· blocks 1
#75
execOrders
· blocks 2
#49
0xe3a3c9cc
#59
0x0c7abd22
· blocks 2
#76
execOrders
· blocks 1
#61
0xed82b078
· blocks 1
#78
execOrders
#62
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w0
12
w1
13
w0
14
w2
15
w2
18
w3
25
w0
26
w1
28
w3
31
w0
49
w4
58
w1
59
w4
61
w5
62
w6
64
w1
75
w3
76
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1faba556…9dea
0xd32edf…ff58
7 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xc7ea2751…3347
0x3bd359…433a
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:
Kuru Exchange: Market-MON/USDC
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity