pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,348,102
← previous block
next block →
recent activity
Analyzing
Block #73,348,102
11 transactions · 10 stateful · 2026-05-09 00:20:37 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,348,102
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xbbb036a8
· blocks 1
#4
0x69fe7e4c
#5
0x69fe7e4c
#6
updatePrices
#7
0x39435dac
#8
updateDataFeedsValuesPartial
#9
0xeffdedb0
#10
setData
#3
0x575c0012
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b9c6652…d14e
0x754704…b603
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x54c30e24…70dd
0x065c9d…c394
2 touches
0 conflicts
0x576b9d47…4ae8
0x065c9d…c394
2 touches
0 conflicts
0xb7bff595…2555
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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:
USDC (USDC)
1 conflict on slot
0x2b9c66521e…35d14e
Audit this contract →
← previous block
·
next block →
recent activity