pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,054,698
← previous block
next block →
recent activity
Analyzing
Block #86,054,698
42 transactions · 27 stateful · 2026-07-06 21:09:57 UTC
Parallelism
88
/100
Blocked
37
%
Avg conflicts / tx
0.4
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,054,698
· 42 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x6a4c1a1d
#7
0x6a4c1a1d
#8
0x50a0b275
· blocks 2
#9
0x6a4c1a1c
#10
0x6a4c1a1c
#11
0xcf7468f4
#12
0x0c7abd22
#13
0x6a4c1a1c
#14
0xaf5e395a
· blocks 1
#15
0xd2116f31
#16
0xab083028
· blocks 3
#17
0xab083028
#18
0xab083028
#20
forward
#21
updateDataFeedsValuesPartial
#22
0x6a4c1a1c
#23
execOrders
· blocks 2
#25
0x6a4c1a1c
#26
execPerpOps
#28
0x3f5c179b
#29
0x3f5c179b
· blocks 2
#34
forward
#35
forward
#37
0xed82b078
#38
setData
#41
0xc7e3ec2c
#19
0xab083028
· blocks 2
#24
execOrders
· blocks 1
#32
0xed82b078
· blocks 1
#33
createModule
#27
execFwdPositionOps
· blocks 1
#30
0x3f5c179b
· blocks 1
#36
0xed82b078
#31
batchUpdate
#39
execOrders
· blocks 1
#40
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
14
w0
16
w0
19
w1
23
w0
24
w1
27
w2
29
w0
30
w2
31
w3
32
w1
33
w1
36
w2
39
w3
40
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x46005a44…f34b
0xa6afd3…d132
8 touches
6 conflicts
0x61377ba1…0bef
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1e166a45…98a7
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
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: Market-WETH/USDC
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity