pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,360,451
← previous block
next block →
recent activity
Analyzing
Block #73,360,451
10 transactions · 7 stateful · 2026-05-09 01:42:40 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,360,451
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
exactInputSingle
#4
forward
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
0xeffdedb0
#9
setData
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x07396e24…1fea
0x065c9d…c394
2 touches
0 conflicts
0x64dd94af…c64b
0x065c9d…c394
2 touches
0 conflicts
0x9970c566…b6bd
0x065c9d…c394
2 touches
0 conflicts
0xab6c495a…75e9
0x065c9d…c394
2 touches
0 conflicts
0xb317f64e…efb8
0x065c9d…c394
2 touches
0 conflicts
0xe50d11b1…231c
0x065c9d…c394
2 touches
0 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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity