pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,067,175
← previous block
next block →
recent activity
Analyzing
Block #101,067,175
37 transactions · 26 stateful · 2026-09-01 14:34:22 UTC
Parallelism
86
/100
Blocked
58
%
Avg conflicts / tx
0.59
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,067,175
· 37 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x1ada0a83
· blocks 1
#3
execute
#4
0xab083028
· blocks 4
#5
0x0c7abd22
#6
0x67098489
#7
matchOrders
#8
updatePrices
· blocks 1
#11
0x4297b034
· blocks 1
#13
0x8263f5d9
#14
execOrders
· blocks 2
#17
0x0c7abd22
· blocks 2
#19
0x6a96e2e5
#20
0xb414539a
#21
0xe3a3c9cc
#22
0x0c7abd22
#23
0x0c7abd22
#24
0x0c7abd22
#25
setData
· blocks 1
#27
0x62be7533
#33
0x6a96e2e5
#34
execOrders
#2
executePacked
#9
updatePrices
#10
0xab083028
· blocks 2
#15
execOrders
· blocks 1
#18
0x0c7abd22
· blocks 1
#26
setData
#28
0x3f5c179b
· blocks 1
#12
0x8263f5d9
#16
execOrders
· blocks 2
#29
0x3f5c179b
#32
0xed82b078
#35
execOrders
· blocks 1
#30
execFwdPositionOpsV2
· blocks 2
#31
execFwdPositionOpsV2
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
8
w0
9
w1
10
w1
11
w0
12
w2
14
w0
15
w1
16
w2
17
w0
18
w1
25
w0
26
w1
28
w1
29
w2
30
w3
31
w4
32
w2
35
w2
36
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x451e482b…7e7d
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
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: MarginAccount
3 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity