pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,598,155
← previous block
next block →
recent activity
Analyzing
Block #73,598,155
38 transactions · 27 stateful · 2026-05-10 04:03:39 UTC
Parallelism
84
/100
Blocked
59
%
Avg conflicts / tx
0.79
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,598,155
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute_route
· blocks 3
#4
0xbbb036a8
#5
0x575c0012
#6
0x575c0012
#7
0x6a000413
#8
0x121eab2f
#9
execute
#10
0x6a000413
#11
0x6a000413
#12
exactOutputSingle
#14
updatePrices
· blocks 1
#16
updatePrices
#17
updatePrices
#18
updatePrices
#19
0xe7be4706
· blocks 1
#20
0xe7be4706
#22
0x98717539
· blocks 3
#27
0x0c7abd22
· blocks 5
#33
updateDataFeedsValuesPartial
#34
setData
#35
0x6a000413
#2
execute_route
· blocks 2
#15
updatePrices
#21
0xe7be4706
#23
0x98717539
· blocks 1
#28
0x0c7abd22
· blocks 4
#36
0x39435dac
· blocks 1
#3
execute_route
#13
execute
#24
0x98717539
· blocks 2
#29
0x0c7abd22
· blocks 3
#37
0x39435dac
#25
0x98717539
· blocks 1
#30
0x0c7abd22
· blocks 2
#26
0x98717539
#31
0x0c7abd22
· blocks 1
#32
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
13
w2
14
w0
15
w1
19
w0
21
w1
22
w0
23
w1
24
w2
25
w3
26
w4
27
w0
28
w1
29
w2
30
w3
31
w4
32
w5
36
w1
37
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a26a93f…e947
0xd32edf…ff58
11 touches
15 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
6 touches
3 conflicts
0xd49762c9…1359
0x34b655…2a6f
6 touches
3 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
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:
0xd32edf66…9fff58
15 conflicts on slot
0x9a26a93fd2…87e947
Audit this contract →
← previous block
·
next block →
recent activity