pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,560,458
← previous block
next block →
recent activity
Analyzing
Block #89,560,458
33 transactions · 28 stateful · 2026-07-23 03:52:00 UTC
Parallelism
76
/100
Blocked
57
%
Avg conflicts / tx
1.06
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,560,458
· 33 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 3
#2
0x5d66ef…3b13
#3
0x50a0b275
#4
0xaf5e395a
#5
0xcf7468f4
#9
0x0c7abd22
· blocks 3
#13
0x6b8f732b
· blocks 1
#15
0x5a5d9a99
· blocks 3
#16
execFwdPositionOps
· blocks 1
#17
0x62be7533
#19
updateDataFeedsValuesPartial
#24
0xed82b078
#25
updateTemporalNumericValuesV1
#26
setData
#27
execOrders
· blocks 4
#32
0xc7e3ec2c
#6
executePacked
· blocks 1
#7
0xab083028
· blocks 2
#10
0x0c7abd22
· blocks 2
#14
0x6b8f732b
#18
execFwdPositionOps
· blocks 4
#23
execOrders
#8
0xab083028
#11
0x0c7abd22
· blocks 1
#20
execFwdPositionOps
· blocks 2
#21
batchUpdate
#12
0x0c7abd22
#22
execFwdPositionOps
· blocks 2
#28
execOrders
· blocks 3
#29
execOrders
· blocks 2
#30
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w1
8
w2
9
w0
10
w1
11
w2
12
w3
13
w0
14
w1
15
w0
16
w0
18
w1
20
w2
21
w2
22
w3
23
w1
28
w4
30
w6
31
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xe0566ad7…995b
0xd32edf…ff58
7 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity