pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,258,687
← previous block
next block →
recent activity
Analyzing
Block #86,258,687
39 transactions · 29 stateful · 2026-07-07 19:51:42 UTC
Parallelism
85
/100
Blocked
45
%
Avg conflicts / tx
0.67
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,258,687
· 39 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute
#2
0x50a0b275
#3
0x6bdec372
#4
0x575c0012
#5
0x1094dc9f
#6
0x6a4d5946
· blocks 1
#7
0x6a4d5946
#8
0xab083028
· blocks 4
#13
updatePrices
#14
updatePrices
#15
updatePrices
#16
execOrders
· blocks 3
#19
updateDataFeedsValuesPartial
#20
updateDataFeedsValuesPartial
#21
0x6a4d5945
#22
execPerpOps
#24
0x62be7533
#25
execFwdPositionOps
#27
0x0c7abd22
#31
cancel
#32
0x4d6611…e4cb
#33
setData
#34
0x6a4d5945
#37
jMMeC
#38
0xc7e3ec2c
#9
0xab083028
· blocks 3
#17
execOrders
· blocks 2
#23
0x6a4d5946
#10
0xab083028
· blocks 4
#18
execOrders
· blocks 3
#11
0xab083028
· blocks 3
#28
execFwdPositionOps
· blocks 1
#30
execFwdPositionOps
#12
0x6ad2e98b
#26
0x3f5c179b
· blocks 1
#35
execOrders
· blocks 1
#29
0xed82b078
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w0
9
w1
10
w2
11
w3
12
w4
16
w0
17
w1
18
w2
23
w1
26
w4
28
w3
29
w5
30
w3
35
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xec0e0220…cb90
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x202c03eb…cf33
0xa6afd3…d132
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x213ee207…a151
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: MarginAccount
10 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity