pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,469,457
← previous block
next block →
recent activity
Analyzing
Block #73,469,457
9 transactions · 7 stateful · 2026-05-09 13:48:10 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,469,457
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x121eab2f
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePriceFeedsIfNecessary
#8
withdraw
#3
0x121eab2f
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
0xe1b51a09…9c3c
0x065c9d…c394
4 touches
1 conflict
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0xe7535190…5a0f
0x6c4bfa…a540
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 touches
1 conflict
0x00000000…000b
0x6c4bfa…a540
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
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
0xe1b51a092e…c19c3c
Audit this contract →
← previous block
·
next block →
recent activity