pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,318,650
← previous block
next block →
recent activity
Analyzing
Block #73,318,650
27 transactions · 20 stateful · 2026-05-08 21:04:43 UTC
Parallelism
78
/100
Blocked
50
%
Avg conflicts / tx
0.63
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,318,650
· 27 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#6
execute_route
· blocks 3
#9
execute
#10
0x69fe5063
#11
0x4ec9f7a2
#12
0x69fe5063
#13
execute
#14
exactInputSingle
#17
updatePrices
· blocks 1
#19
0xe7be4706
#20
0xe7be4706
#21
0x000000b2
#22
updateDataFeedsValuesPartial
#23
setData
#25
0xeffdedb0
#26
0x39435dac
#2
0x0c7abd22
· blocks 3
#7
execute_route
· blocks 1
#16
execute
#18
updatePrices
#3
0x0c7abd22
· blocks 2
#8
execute_route
· blocks 1
#4
0x0c7abd22
· blocks 1
#15
exactInputSingle
#5
0x0c7abd22
· blocks 1
#24
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
6
w0
7
w1
8
w2
15
w3
16
w1
17
w0
18
w1
24
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fb7fed…c34b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x11998eac…f9a4
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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:
0xd32edf66…9fff58
10 conflicts on slot
0xe6fb7fed45…43c34b
Audit this contract →
← previous block
·
next block →
recent activity