pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,917,914
← previous block
next block →
recent activity
Analyzing
Block #73,917,914
12 transactions · 9 stateful · 2026-05-11 15:49:03 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,917,914
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
claim
#2
0x1094dc9f
#3
0x0c7abd22
· blocks 2
#5
0x98717539
#6
withdraw
#8
updatePriceFeedsIfNecessary
#9
updateDataFeedsValuesPartial
#10
0x6a01fae7
#11
setData
#4
0x0c7abd22
· blocks 1
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x915f67ef…d232
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x98191c…db16
2 touches
0 conflicts
0x00000000…0001
0xa9fcce…72c1
2 touches
0 conflicts
0x00000000…0006
0xa9fcce…72c1
2 touches
0 conflicts
0x00b6116f…48a4
0xa9fcce…72c1
2 touches
0 conflicts
0x00f5139a…fb75
0xa9fcce…72c1
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
3 conflicts on slot
0x915f67efed…92d232
Audit this contract →
← previous block
·
next block →
recent activity