pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,651,016
← previous block
next block →
recent activity
Analyzing
Block #73,651,016
11 transactions · 9 stateful · 2026-05-10 09:58:00 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,651,016
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0xe7be4706
#5
setData
#6
0x5339c59f
#7
0xed82b078
· blocks 2
#10
0x39435dac
#8
0xed82b078
· blocks 1
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05614958…155a
0x065c9d…c394
2 touches
0 conflicts
0x0902ec85…4db2
0x065c9d…c394
2 touches
0 conflicts
0x39263586…08ba
0x065c9d…c394
2 touches
0 conflicts
0x39e9ce32…cb42
0x065c9d…c394
2 touches
0 conflicts
0x3d4bdd68…73d5
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity