pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,396,074
← previous block
next block →
recent activity
Analyzing
Block #73,396,074
10 transactions · 8 stateful · 2026-05-09 05:39:44 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,396,074
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x69fec918
#6
0xeffdedb0
#7
setData
#8
0x39435dac
#9
0x39435dac
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e766fad…79a6
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x8e764f…e322
4 touches
1 conflict
0x5b3dfef8…a676
0x8e764f…e322
4 touches
1 conflict
0xaa03918c…f1c7
0x8e764f…e322
4 touches
1 conflict
0x7fb38b87…dd60
0x065c9d…c394
4 touches
1 conflict
0x88cca774…0887
0x065c9d…c394
4 touches
1 conflict
0xf92b6c60…f499
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
0x4e766fadab…4b79a6
Audit this contract →
← previous block
·
next block →
recent activity