pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,670,750
← previous block
next block →
recent activity
Analyzing
Block #73,670,750
12 transactions · 10 stateful · 2026-05-10 12:11:04 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,670,750
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#2
exactInput
· blocks 1
#3
0x6a007650
#6
updatePrices
#7
0x98717539
· blocks 1
#8
setData
#9
updateDataFeedsValuesPartial
#10
0x6a007650
#4
exactInputSingle
#5
execute
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w1
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
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:
0x63e48b72…8c53f2
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity