Percentage blocked is primarily driven by your clients and their DNS activity.
If clients repeatedly request domains that are not blocked, that drives the rate down. An example would be spending a lot of time every day on pi-hole.net, which should contain no blocked domains.
Alternatively, if you frequently visit commercial websites that are chock full of ads (cnn.com, dailymail.uk, etc), your percentage blocked will go right up.
If you have clients that repeatedly request a blocked domain (IOT devices are frequent offenders), that can also quickly drive up your percentage blocked.
This would indicate that either the ads cannot be blocked by Pi-hole (they are served from the same domains as the content), or the client is not using Pi-hole for DNS. You could also be using a browser with secure or private browsing enabled, which sneds DNS traffic to a DNS other than Pi-hole.
These tools can help you determine the source of ads:
You can also see which DNS server a client is using with these commands:
From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
nslookup pi.hole
nslookup flurry.com
In your specific case, you have IP's on two separate interfaces, and the IP's are on different private IP ranges:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ddi.msc-net.co.jp is 0.0.0.0 on lo (127.0.0.1)
[✓] ddi.msc-net.co.jp is 0.0.0.0 on enx002427fe4ab6 (192.168.0.92)
[✓] ddi.msc-net.co.jp is 0.0.0.0 on wlan0 (192.168.14.92)
[✓] doubleclick.com is 172.217.168.174 via a remote, public DNS server (8.8.8.8)
Pi-hole is configured for the ethernet connection:
PIHOLE_INTERFACE=enx002427fe4ab6
You have two DHCP servers operating on your network, and it doesn't appear that either is passing the IP of Pi-hole as DNS server:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 300 bytes from enx002427fe4ab6:192.168.0.101
Offered IP address: 192.168.0.117
Server IP address: 192.168.0.101
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
lease-time: 14400 ( 4h )
server-identifier: 192.168.0.101
--- end of options ---
* Received 300 bytes from wlan0:192.168.14.1
Offered IP address: 192.168.14.220
Server IP address: 192.168.14.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
lease-time: 14400 ( 4h )
server-identifier: 192.168.14.1
--- end of options ---
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 1
DHCP packets received on interface enx002427fe4ab6: 1