pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,446,984
← previous block
next block →
recent activity
Analyzing
Block #73,446,984
7 transactions · 5 stateful · 2026-05-09 11:18:34 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,446,984
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#4
swapAndStartBridgeTokensViaMayan
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
0xce0b38b5…b07a
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x02068a29…2f8b
0x065c9d…c394
2 touches
0 conflicts
0x106acd3a…1a29
0x065c9d…c394
2 touches
0 conflicts
0x6aa05966…88ed
0x065c9d…c394
2 touches
0 conflicts
0x6ae4f2d1…7114
0x065c9d…c394
2 touches
0 conflicts
0x98c463b9…fbd6
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xce0b38b5d2…37b07a
Audit this contract →
← previous block
·
next block →
recent activity