pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,594,278
← previous block
next block →
recent activity
Analyzing
Block #73,594,278
17 transactions · 12 stateful · 2026-05-10 03:37:53 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,594,278
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#3
0x69fffe09
#4
removeLiquidity
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
0x98717539
#11
setData
#12
exactInputSingle
#13
0x62be7533
#14
updatePosition
#15
0x0c7abd22
#16
0x69fffe08
#2
0xbbb036a8
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x2b9c6652…d14e
0x754704…b603
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x7e220431…dd31
0x5afd3e…7620
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:
0x754704bc…afb603
1 conflict on slot
0x9a55547719…9719a8
Audit this contract →
← previous block
·
next block →
recent activity