pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,215,039
← previous block
next block →
recent activity
Analyzing
Block #73,215,039
10 transactions · 7 stateful · 2026-05-08 09:35:20 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,215,039
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
transfer
#3
updateDataFeedsValuesPartial
#4
0xed82b078
· blocks 1
#6
0x69fdaed0
#7
setData
#8
exactInputSingle
#9
execOrders
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x849f3e33…c095
0x34b655…2a6f
2 touches
0 conflicts
0x874f5c70…608f
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
2 touches
0 conflicts
0xedb848fe…6534
0x34b655…2a6f
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
0xbd7e37a9b5…859eb5
Audit this contract →
← previous block
·
next block →
recent activity