pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,360,858
← previous block
next block →
recent activity
Analyzing
Block #88,360,858
37 transactions · 28 stateful · 2026-07-17 14:10:38 UTC
Parallelism
78
/100
Blocked
43
%
Avg conflicts / tx
0.68
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,360,858
· 37 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
execute
· blocks 1
#2
executePacked
#3
executePacked
#5
0x50a0b275
#6
0xa96df62f
#7
0x50a0b275
#8
0x50a0b275
#9
0xaf5e395a
· blocks 1
#10
postStateList
#12
updatePrices
#13
0x0c7abd22
#14
execPerpOps
#15
execPerpOps
#16
updatePrices
#17
0x5a5d9a99
· blocks 3
#20
updateDataFeedsValuesPartial
#21
updateDataFeedsValuesPartial
#25
0x62be7533
#27
0x3f5c179b
· blocks 1
#28
0x3f5c179b
#29
0x3f5c179b
#32
0x6a5a3856
· blocks 1
#34
setData
#36
0xc7e3ec2c
#4
executePacked
· blocks 1
#18
0x5a5d9a99
· blocks 4
#30
0xed82b078
#33
0x6a5a3856
#11
0x50a0b275
#19
0x98717539
· blocks 2
#22
execFwdPositionOps
· blocks 5
#23
execFwdPositionOps
· blocks 2
#24
execFwdPositionOps
· blocks 3
#26
execFwdPositionOps
· blocks 1
#31
execFwdPositionOps
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
9
w0
11
w2
17
w0
18
w1
19
w2
22
w3
23
w4
24
w5
26
w6
27
w0
30
w1
31
w6
32
w0
33
w1
35
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2de05d…3e6b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x124be23b…2cca
0x34b655…2a6f
6 touches
3 conflicts
0xf9fd0525…4052
0x34b655…2a6f
6 touches
3 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
3 conflicts on slot
0x9a2de05d75…453e6b
Audit this contract →
← previous block
·
next block →
recent activity