pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,648,670
← previous block
next block →
recent activity
Analyzing
Block #73,648,670
11 transactions · 9 stateful · 2026-05-10 09:42:13 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,648,670
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a00536d
#2
updateDataFeedsValuesPartial
#3
0x785f5745
#4
0x3900b0…a3a5
#5
updatePriceFeedsIfNecessary
#6
0x5339c59f
· blocks 2
#9
setData
#10
0x39435dac
#7
0x5339c59f
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xc8023fc5…7d46
0x0c65a0…0852
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity