pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,464,550
← previous block
next block →
recent activity
Analyzing
Block #73,464,550
10 transactions · 8 stateful · 2026-05-09 13:15:29 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,464,550
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
0x0c7abd22
#3
0x121eab2f
#5
updateDataFeedsValuesPartial
#6
0x54cb092e
#7
0xc5a04723
#8
0x69ff33e8
#9
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x115666ed…d560
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x325f77d5…eaae
0x065c9d…c394
2 touches
0 conflicts
0x36ff9941…d0f1
0x065c9d…c394
2 touches
0 conflicts
0x488cba5c…9655
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:
0x34b6552d…112a6f
1 conflict on slot
0x6eba5e7f6a…ac4b52
Audit this contract →
← previous block
·
next block →
recent activity