pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,636,113
← previous block
next block →
recent activity
Analyzing
Block #83,636,113
35 transactions · 26 stateful · 2026-06-25 16:27:12 UTC
Parallelism
63
/100
Blocked
58
%
Avg conflicts / tx
1.8
Longest chain
13
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,636,113
· 35 txs across 13 waves · depth 13
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
wave
w11
wave
w12
#0
syscallReward
#1
0x50a0b275
#2
exactInputSingle
#3
0x0c7abd22
#4
updatePrices
#5
execOrders
· blocks 8
#6
execPerpOps
#7
execPerpOps
#8
execPerpOps
#9
execPerpOps
#10
0x6b8f732b
#11
updateDataFeedsValuesPartial
#12
0x6b8f732b
#13
0x98717539
· blocks 7
#19
0x0c7abd22
· blocks 2
#23
0x62be7533
#24
0x0c7abd22
#25
setData
#26
0x2a95e1…944d
#34
0xc7e3ec2c
#14
0x5a5d9a99
· blocks 6
#20
0x0c7abd22
· blocks 1
#22
execFwdPositionOps
· blocks 4
#15
0x5a5d9a99
· blocks 5
#21
0x0c7abd22
#16
0x5a5d9a99
· blocks 4
#17
0x5a5d9a99
· blocks 3
#18
0x98717539
· blocks 2
#27
execOrders
· blocks 6
#28
execOrders
· blocks 5
#29
execOrders
· blocks 4
#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
5
w0
13
w0
14
w1
15
w2
16
w3
17
w4
18
w5
22
w1
27
w6
28
w7
32
w11
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x3405238a…68b6
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x95cb8e34…5eba
0x34b655…2a6f
9 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x7c533cc8…0a1e
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity