pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,510,987
← previous block
next block →
recent activity
Analyzing
Block #74,510,987
14 transactions · 10 stateful · 2026-05-14 09:38:09 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,510,987
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xed82b078
#3
revealWithCallback
#4
updatePrices
#5
0x5bf9264c
#6
redeemDelegations
#7
forward
#8
updateDataFeedsValuesPartial
#10
0xd9b38f…ec4e
#11
0x9b1906…79fa
#12
setData
#13
0x39435dac
#9
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde74d6d1…9422
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1caf9add…5784
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0xa4177a39…463f
0x065c9d…c394
2 touches
0 conflicts
0xc36ed1ad…ab46
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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
1 conflict on slot
0xde74d6d1f0…b99422
Audit this contract →
← previous block
·
next block →
recent activity