pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,297,425
← previous block
next block →
recent activity
Analyzing
Block #73,297,425
9 transactions · 7 stateful · 2026-05-08 18:43:25 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,297,425
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x1094dc9f
#4
0x39435dac
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
setData
#2
0x0c7abd22
· blocks 1
#5
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x330df236…25eb
0xa6afd3…d132
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x72b98d34…385c
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xc6a8c250…737d
0x1b6862…e19c
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:
0xa6afd386…b0d132
1 conflict on slot
0x330df23632…e625eb
Audit this contract →
← previous block
·
next block →
recent activity