pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,068,425
← previous block
next block →
recent activity
Analyzing
Block #101,068,425
35 transactions · 30 stateful · 2026-09-01 14:40:45 UTC
Parallelism
83
/100
Blocked
50
%
Avg conflicts / tx
0.94
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,068,425
· 35 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#5
0x6a96e464
#6
0xab083028
#7
exactOutputSingle
#8
exactOutputSingle
#9
execute
#10
0x6a96e464
#11
0x6a96e464
#12
0xb8f7c4…afd8
#13
0x5acec890
· blocks 5
#14
updatePrices
· blocks 2
#17
updatePrices
#18
execOrders
· blocks 1
#22
0x59558d29
#23
execPerpOps
#24
execPerpOps
#25
execFwdPositionOpsV2
· blocks 1
#27
0x3f5c179b
#31
setData
#2
0x0c7abd22
· blocks 4
#15
updatePrices
· blocks 1
#19
execOrders
· blocks 2
#29
execFwdPositionOpsV2
· blocks 2
#3
0x0c7abd22
· blocks 1
#16
updatePrices
#20
0x5acec890
· blocks 2
#32
execOrders
· blocks 2
#4
0x0c7abd22
· blocks 2
#21
0x3e2e8792
· blocks 1
#33
execOrders
· blocks 1
#26
execFwdPositionOpsV2
#28
0xed82b078
· blocks 1
#34
execOrders
#30
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
13
w0
14
w0
15
w1
16
w2
18
w0
19
w1
20
w2
21
w3
26
w4
28
w4
29
w1
30
w5
32
w2
33
w3
34
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d29
0x1b6862…e19c
8 touches
6 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)
6 conflicts on slot
0xd9f18d9a4a…7f141d
Audit this contract →
← previous block
·
next block →
recent activity