pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,272,262
← previous block
next block →
recent activity
Analyzing
Block #86,272,262
35 transactions · 28 stateful · 2026-07-07 21:22:11 UTC
Parallelism
80
/100
Blocked
54
%
Avg conflicts / tx
0.83
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,272,262
· 35 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
0x0c7abd22
#2
0x0c7abd22
#3
0x0c7abd22
#4
0x0c7abd22
· blocks 3
#6
0xbbb036a8
#7
0x6a4d6e7b
#9
updatePrices
#10
updatePrices
#11
execOrders
· blocks 2
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
0x6a4d6e7b
#17
execFwdPositionOps
· blocks 2
#19
0x3f5c179b
#20
0x3f5c179b
· blocks 1
#21
0x3f5c179b
· blocks 3
#26
0x0c72758b
· blocks 1
#28
setData
#34
0x5d2fd812
#5
0x0c7abd22
· blocks 1
#8
execute
#12
execOrders
· blocks 1
#18
execFwdPositionOps
#22
0xed82b078
· blocks 2
#23
0xed82b078
· blocks 2
#27
0x0c72758b
#16
0x0c7abd22
#24
0xed82b078
· blocks 1
#29
execOrders
· blocks 4
#25
0xed82b078
#30
execOrders
· blocks 3
#31
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w1
11
w0
12
w1
16
w2
17
w0
18
w1
20
w0
21
w0
22
w1
23
w1
24
w2
25
w3
26
w0
27
w1
29
w2
30
w3
31
w4
32
w5
33
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x46b62326…9b3c
0xa6afd3…d132
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0x9e7f288e…1a24
0x34b655…2a6f
6 touches
3 conflicts
0x1621e4ab…d208
0xd32edf…ff58
5 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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity