pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,396,646
← previous block
next block →
recent activity
Analyzing
Block #73,396,646
10 transactions · 10 stateful · 2026-05-09 05:43:34 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,396,646
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0x121eab2f
#3
execute
#4
updateDataFeedsValuesPartial
#5
0xe7be4706
· blocks 1
#7
setData
#8
0x69fec9fd
#9
0xeffdedb0
#6
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0e61e9f8…3db6
0x065c9d…c394
2 touches
0 conflicts
0x1f4e73e8…08ed
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
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:
0x3bd359c1…15433a
1 conflict on slot
0x0d0b2509ae…4b074d
Audit this contract →
← previous block
·
next block →
recent activity