pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,500,041
← previous block
next block →
recent activity
Analyzing
Block #73,500,041
11 transactions · 9 stateful · 2026-05-09 17:11:39 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.45
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,500,041
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
· blocks 3
#2
updatePrices
#3
0x16040cc9
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#9
0x69ff6b43
#10
setData
#4
0xed82b078
· blocks 2
#7
0x5339c59f
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w2
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x65099a49…7fcc
0x065c9d…c394
3 touches
1 conflict
0x210fa626…1744
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x523eb8c7…2b35
0x065c9d…c394
2 touches
0 conflicts
0xa9287840…1e02
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
3 conflicts on slot
0x4d87512b00…43897c
Audit this contract →
← previous block
·
next block →
recent activity