pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,308,350
← previous block
next block →
recent activity
Analyzing
Block #73,308,350
9 transactions · 8 stateful · 2026-05-08 19:56:07 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,308,350
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
updatePosition
#4
updateDataFeedsValuesPartial
#6
0x69fe404f
#7
0xeffdedb0
#8
setData
#3
0xed82b078
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x69518ce5…7ed6
0x065c9d…c394
3 touches
1 conflict
0x151af2a0…b509
0x065c9d…c394
2 touches
0 conflicts
0x2f66fbf9…a1ff
0x065c9d…c394
2 touches
0 conflicts
0x58af8a5b…72c4
0x065c9d…c394
2 touches
0 conflicts
0xa44fedb0…2daa
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
0xbd7e37a9b5…859eb5
Audit this contract →
← previous block
·
next block →
recent activity