pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,439,028
← previous block
next block →
recent activity
Analyzing
Block #91,439,028
34 transactions · 31 stateful · 2026-07-29 20:28:53 UTC
Parallelism
74
/100
Blocked
55
%
Avg conflicts / tx
1.06
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,439,028
· 34 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xab083028
#5
0x6a6a62fc
#6
execPerpOps
#7
execPerpOps
#8
updatePrices
· blocks 1
#10
0x5a5d9a99
· blocks 7
#15
updateDataFeedsValuesPartial
#18
execFwdPositionOps
#19
swapTokensSingleV3ERC20ToNative
#20
0x94defb17
#22
forward
#28
setData
#31
0x6a6a62fc
#32
0x59558d29
#33
0xc7e3ec2c
#2
0x0c7abd22
· blocks 3
#9
updatePrices
#11
0x5a5d9a99
· blocks 4
#16
execFwdPositionOps
· blocks 3
#4
0xab083028
· blocks 2
#12
0x5a5d9a99
· blocks 4
#23
0xed82b078
· blocks 1
#24
execOrders
#13
0x5a5d9a99
· blocks 1
#25
0xed82b078
· blocks 2
#14
0x5a5d9a99
· blocks 3
#26
0xed82b078
#27
0xed82b078
#17
execFwdPositionOps
· blocks 2
#21
execFwdPositionOps
· blocks 1
#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
4
w2
8
w0
9
w1
10
w0
11
w1
12
w2
13
w3
14
w4
16
w1
17
w5
21
w6
23
w2
24
w2
25
w3
26
w4
27
w4
29
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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:
Perpl
10 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity