pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,429,750
← previous block
next block →
recent activity
Analyzing
Block #74,429,750
12 transactions · 11 stateful · 2026-05-14 00:36:39 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,429,750
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xa96df62f
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
updateFeeds
#8
exactInputSingle
#9
transferFrom
#10
setData
#11
0x39435dac
#2
0x0c7abd22
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
0x4b42341b…11b1
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1a930b5a…efce
0x065c9d…c394
2 touches
0 conflicts
0x3a07a47c…5c74
0x065c9d…c394
2 touches
0 conflicts
0x9c00c985…0dc6
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x4b42341b82…7611b1
Audit this contract →
← previous block
·
next block →
recent activity