pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,811,085
← previous block
next block →
recent activity
Analyzing
Block #90,811,085
36 transactions · 33 stateful · 2026-07-27 15:46:38 UTC
Parallelism
75
/100
Blocked
55
%
Avg conflicts / tx
1.11
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,811,085
· 36 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
0x6a677dd6
· blocks 1
#4
postStateList
#7
execPerpOps
#8
execPerpOps
#9
updatePrices
· blocks 1
#11
0x5a5d9a99
· blocks 7
#16
updateDataFeedsValuesPartial
#18
0x3f5c179b
#19
executeBatch
#20
0x3f5c179b
· blocks 1
#22
forward
#26
setData
#30
execOrders
#32
0x59558d29
· blocks 1
#34
0xc7e3ec2c
#35
0xc7e3ec2c
#3
0x6a677dd6
#5
0xab083028
· blocks 1
#6
0x0c7abd22
#10
updatePrices
#12
0x5a5d9a99
· blocks 6
#21
0xed82b078
#33
0x59558d29
#13
0x5a5d9a99
· blocks 5
#23
0xed82b078
#14
0x5a5d9a99
· blocks 3
#25
execOrders
· blocks 1
#15
0x5a5d9a99
· blocks 2
#17
execFwdPositionOps
· blocks 3
#24
execFwdPositionOps
#27
execOrders
· blocks 3
#28
execOrders
· blocks 2
#29
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
6
w1
9
w0
10
w1
11
w0
12
w1
13
w2
14
w3
15
w4
17
w4
23
w2
25
w3
27
w5
29
w7
31
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0xa27f1875…0c5d
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb05ef19c…dc4f
0x34b655…2a6f
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:
Perpl
10 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity