pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,652,043
← previous block
next block →
recent activity
Analyzing
Block #73,652,043
14 transactions · 8 stateful · 2026-05-10 10:04:54 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,652,043
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
0x0c7abd22
· blocks 1
#8
forward
#10
updateDataFeedsValuesPartial
#11
0x6a0058bd
#12
setData
#13
0x39435dac
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01affd75…980b
0x065c9d…c394
2 touches
0 conflicts
0x0ee6990a…884e
0x065c9d…c394
2 touches
0 conflicts
0x4dbeaa94…030b
0x065c9d…c394
2 touches
0 conflicts
0x6800eb51…ab70
0x065c9d…c394
2 touches
0 conflicts
0x7f81fb82…633e
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity