get_header for relay.ethgas.com reports inflated number

Every single get_header value from relay.ethgas.com is inflated by `1.1e22`.
Not sure if this is something that is collected wrong or a relay issue but reporting it just in case.

```
fn=2026-03-01_all.csv
clickhouse local -q "SELECT source_type, slot, value, relay from '$fn' where value > 1e21"
0 13791600 1.100000400268666e22 relay.ethgas.com
0 13791603 1.1000005947612107e22 relay.ethgas.com
0 13791604 1.1000009899927117e22 relay.ethgas.com
0 13791611 1.1000004841229676e22 relay.ethgas.com
0 13791621 1.1000005685172473e22 relay.ethgas.com
0 13791636 1.1000004041298963e22 relay.ethgas.com
0 13791641 1.1000001061388357e22 relay.ethgas.com
0 13791760 1.1000004808845625e22 relay.ethgas.com
0 13791774 1.1000004093013821e22 relay.ethgas.com
0 13791796 1.1000003575318277e22 relay.ethgas.com
0 13791821 1.1000003897578324e22 relay.ethgas.com
0 13791826 1.1000003384924743e22 relay.ethgas.com
0 13791827 1.1000002297108128e22 relay.ethgas.com
0 13791831 1.1000002061144085e22 relay.ethgas.com
0 13791832 1.1000003469400632e22 relay.ethgas.com
0 13791873 1.1000001974561946e22 relay.ethgas.com
0 13791964 1.1000006111225402e22 relay.ethgas.com
```

```
clickhouse local -q "SELECT source_type, slot, value, relay from '$fn' where value < 1e21 AND source_type = 0 AND relay = 'relay.ethgas.com'"
```
outputs nothing

Start by reproducing the ClickHouse queries against the 2026-03-01 CSV and trace how get_header values from relay.ethgas.com are collected and represented. Compare the relay response with the stored values to determine whether the inflation is introduced by relayscan or the relay; done means the source is identified and the reported values are corrected or clearly documented.

Written by the indexing model from the issue text.