pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,270,768
← previous block
next block →
recent activity
Analyzing
Block #73,270,768
15 transactions · 7 stateful · 2026-05-08 15:46:05 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,270,768
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe05b4
#2
0x69fe05b4
#3
0x121eab2f
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
0x54cb092e
#12
updateDataFeedsValuesPartial
#13
0xeffdedb0
#14
setData
#11
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf72c7b20…28f3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xef54a158…d802
0x065c9d…c394
3 touches
1 conflict
0x7a9e4c19…bee1
0x065c9d…c394
3 touches
1 conflict
0x49b16333…f558
0x065c9d…c394
3 touches
1 conflict
0x22dbf14a…223d
0x065c9d…c394
3 touches
1 conflict
0x486853ad…69df
0x065c9d…c394
3 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
0xf72c7b2035…3428f3
Audit this contract →
← previous block
·
next block →
recent activity