pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,395,982
← previous block
next block →
recent activity
Analyzing
Block #73,395,982
13 transactions · 11 stateful · 2026-05-09 05:39:07 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,395,982
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fec8f3
#2
requestRedeem
#3
0x69fec8f3
#4
updatePrices
#5
0xed82b078
· blocks 2
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0xeffdedb0
#11
setData
#12
0x785f5745
#6
0xed82b078
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x361f7db1…4465
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x4ed93a08…4317
0x065c9d…c394
2 touches
0 conflicts
0x8214bbed…96ec
0x065c9d…c394
2 touches
0 conflicts
0xa7e16fce…c1eb
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity