pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,104,790
← previous block
next block →
recent activity
Analyzing
Block #102,104,790
37 transactions · 29 stateful · 2026-09-05 05:43:08 UTC
Parallelism
84
/100
Blocked
55
%
Avg conflicts / tx
0.78
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,104,790
· 37 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x4ccf0801
· blocks 1
#2
0xab083028
· blocks 5
#3
0x6a9babef
#4
updatePrices
· blocks 2
#10
0x8263f5d9
#12
0x8263f5d9
#13
execOrders
· blocks 1
#15
0x5acec890
#16
0x5acec890
#18
0x5acec890
#19
0x5acec890
#20
0x5acec890
#22
execOrder
#23
execOrder
· blocks 2
#25
0x59558d29
#26
0x6e1f3a01
#27
setData
#28
execFwdPositionOpsV2
#32
0x57368ddf
#34
0x6a9babef
#5
updatePrices
· blocks 1
#7
0xab083028
· blocks 2
#9
0x4297b034
· blocks 2
#14
execOrders
· blocks 3
#24
0x4cb2db39
#6
updatePrices
#8
0xab083028
· blocks 1
#17
0x5acec890
· blocks 3
#11
0xab083028
· blocks 1
#21
0x5acec890
· blocks 1
#29
execFwdPositionOpsV2
· blocks 3
#30
execFwdPositionOpsV2
#31
0x0c7abd22
#33
execFwdPositionOpsV2
#35
execOrders
· blocks 1
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w0
5
w1
6
w2
7
w1
8
w2
9
w1
11
w3
13
w0
14
w1
17
w2
21
w3
23
w0
24
w1
29
w3
30
w4
31
w4
35
w4
36
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x670c7d3a…71ae
0x34b655…2a6f
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
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity