pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,491,457
← previous block
next block →
recent activity
Analyzing
Block #73,491,457
10 transactions · 8 stateful · 2026-05-09 16:14:35 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,491,457
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
updateDataFeedsValuesPartial
#5
0x98717539
#6
execute
#7
setData
#8
updatePriceFeedsIfNecessary
#9
0x69ff5de3
#2
0x9609049f
· blocks 1
#4
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x689c9587…0e5b
0x065c9d…c394
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x867a2cdf…7d67
0xa6afd3…d132
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
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
0x689c958706…a20e5b
Audit this contract →
← previous block
·
next block →
recent activity