pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,664,077
← previous block
next block →
recent activity
Analyzing
Block #73,664,077
8 transactions · 6 stateful · 2026-05-10 11:26:00 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,664,077
· 8 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
updateDataFeedsValuesPartial
#7
setData
#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
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6c4bfa…a540
4 touches
1 conflict
0x50997ada…364d
0x6c4bfa…a540
4 touches
1 conflict
0xc5564f8e…f4bf
0x6c4bfa…a540
4 touches
1 conflict
0xf0f673fd…37a7
0x6c4bfa…a540
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x125f4e61…fc86
0x065c9d…c394
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:
0xc8689a47…62ee79
1 conflict on slot
0xed57bddf8e…bd1abf
Audit this contract →
← previous block
·
next block →
recent activity