pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#79,407,551
← previous block
next block →
recent activity
Analyzing
Block #79,407,551
10 transactions · 10 stateful · 2026-06-06 02:06:49 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#79,407,551
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x6a238130
#5
exactInputSingle
#6
0x64480813
#7
setData
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c2d6e1d…391b
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x8c2d6e1d1c…15391b
Audit this contract →
← previous block
·
next block →
recent activity