pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,654,979
← previous block
next block →
recent activity
Analyzing
Block #73,654,979
13 transactions · 10 stateful · 2026-05-10 10:24:44 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,654,979
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 2
#3
execute_route
#4
0x1094dc9f
#5
0x0c7abd22
#6
0x6a005d64
#7
exactOutputSingle
#9
updatePrices
#10
0xe7be4706
#11
updateDataFeedsValuesPartial
#12
setData
#2
execute_route
#8
exactOutputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x659bd0…a9da
4 touches
1 conflict
0x00000000…0002
0x659bd0…a9da
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
2 touches
0 conflicts
0x3a66aff6…c544
0x5afd3e…7620
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
0xd77e90ecbe…1e8c04
Audit this contract →
← previous block
·
next block →
recent activity