pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,393,733
← previous block
next block →
recent activity
Analyzing
Block #73,393,733
10 transactions · 7 stateful · 2026-05-09 05:24:10 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,393,733
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
exactInputSingle
#3
0x45761772
· blocks 1
#5
0x69fec572
#6
0xeffdedb0
#7
setData
#8
0x61633731
#9
0x39435dac
#4
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99845708…8e6b
0x188d58…ea8e
4 touches
1 conflict
0x71275f4c…98e8
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x036b6384…3db0
0x15c2c5…05e6
2 touches
0 conflicts
0x31ef8a2f…deee
0x188d58…ea8e
2 touches
0 conflicts
0x31ef8a2f…deef
0x188d58…ea8e
2 touches
0 conflicts
0x3555d21c…7d22
0x188d58…ea8e
2 touches
0 conflicts
0x8b3f6756…dd08
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:
0x188d586d…f9ea8e
1 conflict on slot
0x99845708c0…008e6b
Audit this contract →
← previous block
·
next block →
recent activity