pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,348,789
← previous block
next block →
recent activity
Analyzing
Block #73,348,789
9 transactions · 9 stateful · 2026-05-09 00:25:11 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,348,789
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x69fe7f5f
#7
0xeffdedb0
#8
setData
#3
0x121eab2f
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bf146e8…f5c1
0x065c9d…c394
2 touches
0 conflicts
0x3e184833…d237
0x065c9d…c394
2 touches
0 conflicts
0x47e16a45…f5d4
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity