pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,352,140
← previous block
next block →
recent activity
Analyzing
Block #88,352,140
33 transactions · 31 stateful · 2026-07-17 13:11:50 UTC
Parallelism
79
/100
Blocked
55
%
Avg conflicts / tx
1
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,352,140
· 33 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
execute_route
#2
0xab083028
· blocks 3
#6
0x6a5a2a8d
#7
execPerpOps
#8
execPerpOps
#9
updatePrices
· blocks 2
#12
0x5a5d9a99
· blocks 3
#15
updateDataFeedsValuesPartial
#17
execFwdPositionOps
#18
0x3f5c179b
#21
execFwdPositionOps
· blocks 3
#24
0x36f359b0
#26
setData
#27
0x85075e…6277
#32
0xc7e3ec2c
#3
0xab083028
· blocks 2
#10
updatePrices
· blocks 1
#13
0x5a5d9a99
· blocks 4
#23
execFwdPositionOps
· blocks 2
#4
0x0c7abd22
· blocks 2
#11
updatePrices
#14
0x98717539
· blocks 1
#16
execFwdPositionOps
#25
execOrders
· blocks 1
#5
0x6ad2e98b
· blocks 2
#19
0x3f5c179b
#28
execOrders
· blocks 3
#20
0x3f5c179b
· blocks 1
#29
execOrders
· blocks 2
#22
batchUpdate
#30
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
9
w0
10
w1
11
w2
12
w0
13
w1
14
w2
16
w2
19
w3
20
w4
21
w0
22
w5
23
w1
25
w2
28
w3
29
w4
30
w5
31
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x62b86e44…980e
0x851145…3f07
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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:
Kuru Exchange: MarginAccount
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity