pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,092,130
← previous block
next block →
recent activity
Analyzing
Block #88,092,130
36 transactions · 29 stateful · 2026-07-16 08:12:09 UTC
Parallelism
81
/100
Blocked
59
%
Avg conflicts / tx
0.92
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,092,130
· 36 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
0x6a5892d0
#2
0x6a5892d0
#3
execute
#4
0xab083028
· blocks 5
#6
0xab083028
#7
0xab083028
#9
updatePrices
· blocks 3
#11
updatePrices
#14
0x5a5d9a99
· blocks 5
#17
permit2TransferAndMulticall
#20
updateDataFeedsValuesPartial
#21
updateDataFeedsValuesPartial
#22
0x6a5892d0
#23
0x6a5892d0
#30
execFwdPositionOps
#31
0x6a5892d0
#32
setData
#33
execOrders
· blocks 2
#5
0xab083028
· blocks 2
#10
updatePrices
· blocks 2
#15
0x5a5d9a99
· blocks 4
#24
0x3f5c179b
· blocks 2
#27
execFwdPositionOps
#8
0x6ad2e98b
#12
updatePrices
· blocks 1
#16
0x5a5d9a99
· blocks 2
#25
0xed82b078
· blocks 1
#26
execFwdPositionOps
#28
0xed82b078
#13
updatePrices
#18
0x98717539
· blocks 1
#29
0xed82b078
#19
0x5a5d9a99
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
9
w0
10
w1
12
w2
13
w3
14
w0
15
w1
16
w2
18
w3
19
w4
24
w1
25
w2
26
w2
27
w1
28
w2
29
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x670ee139…94fc
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x4384dd01…4f99
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
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:
Perpl
10 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity