pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,493,212
← previous block
next block →
recent activity
Analyzing
Block #102,493,212
36 transactions · 31 stateful · 2026-09-06 14:31:21 UTC
Parallelism
78
/100
Blocked
52
%
Avg conflicts / tx
0.94
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,493,212
· 36 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
0xab083028
· blocks 4
#3
0x5acec890
· blocks 4
#4
execOrders
· blocks 2
#6
execOrders
#9
0x0c7abd22
· blocks 4
#10
updatePrices
· blocks 1
#12
0x5acec890
#13
0x5acec890
#15
0x5acec890
#18
0x59558d29
#19
execPerpOps
#20
execPerpOps
#21
0x41a8f47c
#22
0x41a8f47c
#25
execFwdPositionOpsV2
#26
setData
#27
setData
#28
handleOps
#32
execOrders
#2
0xab083028
· blocks 3
#5
execOrders
· blocks 1
#8
0x5acec890
· blocks 2
#11
updatePrices
#17
execOrder
· blocks 2
#7
0xab083028
#14
0x5acec890
· blocks 2
#23
execFwdPositionOpsV2
· blocks 1
#24
0x0c7abd22
· blocks 1
#16
0x5acec890
· blocks 1
#29
0xed82b078
#30
execFwdPositionOpsV2
#31
execOrders
· blocks 3
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w1
7
w2
8
w1
9
w0
10
w0
11
w1
14
w2
16
w3
17
w1
23
w2
24
w2
29
w3
30
w3
31
w4
33
w5
34
w6
35
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcc8b6d32…6601
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x51fc8795…126f
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
0x5f77d60791…b12c84
Audit this contract →
← previous block
·
next block →
recent activity