pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,411,774
← previous block
next block →
recent activity
Analyzing
Block #91,411,774
34 transactions · 30 stateful · 2026-07-29 18:10:52 UTC
Parallelism
79
/100
Blocked
63
%
Avg conflicts / tx
1.15
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,411,774
· 34 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x6ad2e98b
· blocks 2
#4
execPerpOps
#5
0x6a6a42a4
· blocks 1
#7
updatePrices
· blocks 3
#10
updatePrices
#12
0x5a5d9a99
· blocks 5
#17
updateDataFeedsValuesPartial
#18
updateDataFeedsValuesPartial
#19
0x0c7abd22
#27
setData
#28
0x62f17f…1494
#31
execOrders
#32
0x59558d29
#33
0xc7e3ec2c
#2
0xab083028
· blocks 4
#6
0x6a6a42a4
#8
updatePrices
· blocks 2
#13
0x5a5d9a99
· blocks 3
#3
0xab083028
· blocks 2
#9
updatePrices
· blocks 1
#14
0x5a5d9a99
· blocks 3
#22
batchUpdate
· blocks 2
#11
updatePrices
#15
0x5a5d9a99
· blocks 4
#21
execFwdPositionOps
#23
0xed82b078
· blocks 1
#24
0xed82b078
· blocks 2
#16
0x5a5d9a99
· blocks 1
#20
execFwdPositionOps
· blocks 2
#25
0xed82b078
#26
0xed82b078
#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
w1
3
w2
5
w0
6
w1
7
w0
8
w1
9
w2
11
w3
12
w0
13
w1
14
w2
15
w3
16
w4
20
w4
22
w2
23
w3
24
w3
25
w4
26
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xcc9f0531…9b44
0x40c49f…2af0
5 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:
Perpl
10 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity