pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,493,930
← previous block
next block →
recent activity
Analyzing
Block #73,493,930
9 transactions · 9 stateful · 2026-05-09 16:30:59 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,493,930
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
setData
#3
0x0c7abd22
· blocks 1
#4
updateTemporalNumericValuesV1
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
#8
0x69ff61ba
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0afa65d0…2b8e
0x065c9d…c394
2 touches
0 conflicts
0x16724e0f…803a
0x065c9d…c394
2 touches
0 conflicts
0x488cba5c…9655
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x58ebd9e8…150d
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
0x22e295f5d8…ac1bef
Audit this contract →
← previous block
·
next block →
recent activity