pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,483,142
← previous block
next block →
recent activity
Analyzing
Block #73,483,142
9 transactions · 8 stateful · 2026-05-09 15:19:08 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,483,142
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
#2
modifyLiquidities
#3
0xed82b078
· blocks 2
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
setData
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x1f6a4f8c…e9ae
0x065c9d…c394
2 touches
0 conflicts
0x5d28f4a0…23cd
0x065c9d…c394
2 touches
0 conflicts
0x89fe7a44…835f
0x065c9d…c394
2 touches
0 conflicts
0xda78d3c2…d68a
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
0x065c9d…c394
2 touches
0 conflicts
0x16bb2fcd…bea1
0x188d58…ea8e
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