pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,506,965
← previous block
next block →
recent activity
Analyzing
Block #73,506,965
10 transactions · 9 stateful · 2026-05-09 17:57:53 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,506,965
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#3
updatePrices
#4
forward
#5
updatePriceFeedsIfNecessary
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
0x69ff7618
#9
setData
#2
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04a0e43c…3b69
0x065c9d…c394
2 touches
0 conflicts
0x0a499e8e…e338
0x065c9d…c394
2 touches
0 conflicts
0x0ed8197f…8dee
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x2ec66dfa…1cf9
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
0x4d87512b00…43897c
Audit this contract →
← previous block
·
next block →
recent activity