pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,495,962
← previous block
next block →
recent activity
Analyzing
Block #108,495,962
37 transactions · 30 stateful · 2026-09-27 15:02:58 UTC
Parallelism
89
/100
Blocked
57
%
Avg conflicts / tx
0.62
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,495,962
· 37 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x67098489
#2
0x0c7abd22
· blocks 1
#3
0x4ccf0801
· blocks 3
#5
0x5acec890
· blocks 4
#7
0x59558d29
#8
0x59558d29
#11
0x3e2e8792
#12
0x5acec890
#13
0x5acec890
#15
execPerpOps
#16
execPerpOps
#18
updatePrices
· blocks 1
#19
updatePrices
#20
updateDataFeedsValuesPartial
#23
0x84403c1b
#24
executeBatch
#31
setData
#33
0x61d59c2d
#35
execOrders
· blocks 1
#4
0xab083028
· blocks 2
#6
0x4cb2db39
#9
0x5acec890
· blocks 3
#17
execOrders
· blocks 1
#22
execFwdPositionOpsV2
· blocks 1
#25
0xab647912
· blocks 2
#10
0xab083028
· blocks 1
#14
0x928e4afa
· blocks 1
#21
execFwdPositionOpsV2
· blocks 1
#27
0xed82b078
#29
execFwdPositionOpsV2
#30
execOrders
#32
0x61d59c2d
· blocks 1
#26
0x3f5c179b
#28
execFwdPositionOpsV2
#34
0x61d59c2d
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w0
6
w1
9
w1
10
w2
14
w2
17
w1
18
w0
21
w2
22
w1
25
w1
26
w3
27
w2
28
w3
29
w2
30
w2
32
w2
34
w3
35
w0
36
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x08cfec9d…7ef0
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c4
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
6 touches
3 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
6 touches
3 conflicts
0x4c29ecd5…58b6
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: MarginAccount
3 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity