pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,416,635
← previous block
next block →
recent activity
Analyzing
Block #91,416,635
35 transactions · 29 stateful · 2026-07-29 18:35:20 UTC
Parallelism
83
/100
Blocked
62
%
Avg conflicts / tx
1
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,416,635
· 35 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x6a6a485f
· blocks 2
#2
0xab083028
· blocks 2
#5
updatePrices
· blocks 4
#9
0x0c7abd22
#11
0x6a6a485f
#13
updatePrices
#14
0x6a6a4860
#15
updateDataFeedsValuesPartial
#16
execFwdPositionOps
· blocks 5
#20
updatePosition
#21
0x29eed2d3
#22
updateTemporalNumericValuesV1
#27
0x6a6a485f
#28
setData
#31
0x59558d29
· blocks 1
#33
0xc7e3ec2c
· blocks 1
#3
0x6ad2e98b
· blocks 1
#6
updatePrices
· blocks 3
#10
0x6a6a4860
· blocks 1
#17
execFwdPositionOps
· blocks 3
#18
execFwdPositionOps
· blocks 1
#32
0x59558d29
#34
0xc7e3ec2c
#4
0x0c7abd22
#7
updatePrices
· blocks 2
#19
execFwdPositionOps
· blocks 4
#26
0x6a6a4860
#8
updatePrices
· blocks 1
#23
execOrders
· blocks 3
#25
execOrders
#12
updatePrices
#24
execOrders
#29
execOrders
· blocks 1
#30
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w0
6
w1
7
w2
8
w3
10
w1
12
w4
16
w0
17
w1
18
w1
19
w2
24
w4
25
w3
26
w2
29
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x03aa8b26…118a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
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:
0x48cba278…e2b48b
10 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity