wurrly

CustodianInferred

The Prime-funded wallet family

27 registry addresses

Observed portfolio value

Reading balances

No successful balance read yet.

Twenty-seven wallets: the family funded by the Coinbase Prime hot wallet with 0.6M to 9.2M each, which mint sAVAX, export to the P-Chain, withdraw from the Coinbase hot wallet, and all pay identical dust to one sink, plus the wallet that paid Coinbase deposit #1 its first 249,999 AVAX. Together they moved about 30M AVAX, twice AVAT's holdings: a client population, not AVAT. Two addresses the registry once carried here are lookalike dusters and are now excluded. The full account is on the research pages.

Holdings

AVAX and the listed tokens, across the addresses in scopeThe price read has not finished. The quantities below are measured; USD values follow.24 h value change unavailable. No read returns a second valued endpoint 24 hours earlier.

Reading balances

Requested: Registered AVAX and liquid-staking balances. Returned coverage unavailable. Chains requested: C. 27 eligible addresses; none read yet.

Source: Avalanche C-Chain RPC, Wurrly Intel registry. No successful read yet.

Read method

Every figure is summed in exact decimal over one asset key at a time. A chain figure adds the priced holdings measured on that chain; an asset the price read could not answer for is left out of the sum, and the cell says how many were left out. A share is that chain figure over the summed priced holdings in the selected scope, divided at 60 decimal places and shown at two.

The P-Chain balance is one measurement for the whole owner group, so an address row on that chain shows the group note instead of a figure of its own. C-Chain AVAX and P-Chain AVAX are separate asset keys and are never added into one line.

No route this card reads returns a valued endpoint twenty-four hours back over the same addresses and assets, so the 24 h change is unavailable in every row. The price route’s own daily move is the AVAX market, which is a different measurement.

Balance history

History range
Display unit
Requested dates follow the read's own successful timestamp.Daily balance, rebuilt from returned transactions and anchored to the live balance

Reading balance history

Requested: C-Chain AVAX only, daily. Returned coverage unavailable. Chains requested: C. 27 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Transaction count unavailable. Anchor time unavailable.

Current positions. Read time unavailable. Staking positions unavailable for this read.

Reading current staking positions

Read method

The series is rebuilt from the transactions the feeds return and then shifted so its last figure equals the live balance the node reported. The shift is the anchor adjustment, and the reach of the feeds behind it is stated above. Nothing is drawn before that shift is proved.

A day's figure is that UTC day's close: the balance after every movement dated that day.

Historical USD is each slot day's own final recorded close for AVAX, from Coinbase Exchange, joined on the UTC day. A day that has not finished has no close, and no other day's price stands in for it. The C-Chain and P-Chain AVAX are the same asset in that market, so both join the one AVAX close. Price join revision 2026-09-14.

Quantity coverage start unavailable.

Flows

Transfers summed by counterparty over the selected window
Flow window

Reading transfer history

Requested: External AVAX transfers of at least 1 AVAX, summed by counterparty. Returned coverage unavailable. Minimum transfer: 1 AVAX. Chains requested: C. 27 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Read method

A trailing window is the interval from the read’s own time minus 30 periods of 24 hours up to that time. The start instant is excluded and the end instant is included, so two adjacent windows never both count the moment they share. Every figure in a trailing window is summed from the dated transfer rows the read returned, one row at a time, in exact decimal.

The returned history is the source’s own aggregate, summed over every row it read rather than over the rows it sent. It is never filtered by its first and last date to make a trailing total: a window that the returned rows cannot reach is reported as unavailable instead.

Inflow is AVAX this subject received and outflow is AVAX it sent. A movement with this subject on both sides is internal and is counted but never summed into an external total; a row with this subject on neither side is unmatched and is counted the same way. A row the feeds dated unreadably belongs to no trailing window, and the count of those is stated above.

Every amount on this card arrived from the source as a JavaScript number, so the sums are exact over the figures received and the received figures are not exact to the last digit of the chain. Each row’s Details says so beside the figure it applies to.

Transfers

Returned transfers, newest firstMinimum transfer: 1 AVAX

Reading transfer history

Requested: Returned AVAX transfers of at least 1 AVAX, newest first, including movements between the subject's own addresses. Returned coverage unavailable. Minimum transfer: 1 AVAX. Chains requested: C. 27 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Read method

These are the transfers the flow read returned, newest first. The same request answers the card above: one read of the source, two measurements of it. Every row is at least 1 AVAX, because the source drops everything below that before it answers, and there are no token rows in it, so no token quantity is ever compared against the numeric 1 of another asset’s unit. A different threshold would need a source that reads to a different depth, which is not a setting on this page.

TRANSFERS shows every returned row, including movements between this subject’s own addresses, each marked Internal. A subject’s own P-Chain key counts as its own in both spellings, so a wallet moving value between its C-Chain and P-Chain sides is Internal rather than a pair of external flows to itself. INFLOW and OUTFLOW are external directions relative to this subject and exclude those rows, and they exclude rows with this subject on neither side and rows whose other endpoint is a chain rather than an address, which have no direction to sort into. CROSS-CHAIN holds the movements between two Avalanche chains: two endpoint chains that differ, or the atomic feed, which returns nothing else.

No pair identifier reaches this page, so a cross-chain export and its matching import are two rows with two amounts and two links. Nothing on this card adds them into one movement, and no figure here counts a pair once.

A historical USD value is that row’s own UTC day’s final closing price multiplied by its exact quantity. A day that has not finished has no close and says so; a day the price read did not return says so separately. Today’s price is never substituted for either.

Pages are windows on the frozen read named in the footer. A newer read landing while you are reading does not replace these rows; it offers itself at the top of the card, and adopting it returns to page 1.

Visualizer

Registry addresses as boxes, and the transfers the read observed between themRegistry addresses are grouped by role. Arrows show transfers returned by the selected read.A counterparty is the address or organisation on the other side of a transfer.

The Prime-funded wallet family. Reading transfers

Visualizer view

The Prime-funded wallet family: registry addresses by role, and the transfers this read observed between them8 boxes and no arrows. Transfer coverage is being read.Exits8 addresses shown of 27 addressesdeposit addresses, exchanges, sinksPrime-family wallet, th…family · C-Chain · Inferred0x7139…25e3Prime-funded family wal…family · C-Chain · Inferred0xc13f…b0edPrime-funded family wal…family · C-Chain · Inferred0xfea1…fbcaPrime-funded family wal…family · C-Chain · Inferred0xa87a…e5f7Prime-funded family wal…family · C-Chain · Inferred0x0128…b6fcPrime-funded family wal…family · C-Chain · Inferred0x3040…9eefPrime-funded family wal…family · C-Chain · Inferred0xd80f…973ePrime-funded family wal…family · C-Chain · Inferred0x9a9e…8431

Select an address to read its identity and observed transfers.

Registry addresses in scope, with each one's role. 27 of 27 addresses read.

Wurrly Intel registry: compiled with this page.

Reading transfers. Transfer coverage is being read.

No transfer read has answered for this scope.

Read method

The boxes are the registry’s own rows, placed by the role the research gave each one: custody first, the working wallets next, the staking and protocol keys, then the exits. Whoever was on the other side of a returned transfer joins an outer column, on the right when this subject paid them and on the left when they only paid in. Grouping is not attribution: a box is named only where the registry names it.

Arrows are the transfers this read returned, summed by pair, asset, chain and kind. Two assets between one pair of boxes are two arrows, never one; a token quantity is never added to an AVAX total and never takes the AVAX reporting threshold. Reverse directions stay apart. A sum is labelled At least only where the source states the depth it reports to and says its coverage was partial; otherwise it is labelled Observed, which is still scoped to this request.

An endpoint the feed left as a chain rather than an address is not a counterparty, so no arrow is drawn to it and the count of transfers that were excluded for that reason is stated in the scope line above.

A column of more than 8 addresses folds its tail behind one control. Folding changes the drawing and nothing else: Connections still lists every canonical relationship, and any movement whose two ends fold into one box is kept as that group’s own internal subtotal, so the arrows plus the subtotals still add up to the same per-asset totals.

Proven: a filed quantity matched to the unit, or a transaction identified by its hash. Inferred: behaviour or timing, with the base rate stated in the source. Candidate: a lead, one tier below inferred, with a written test for promoting it and a written test for killing it. Explorer tag: an explorer's attribution label. Standing describes the cited claim. A transfer alone does not establish ownership.

Minimum transfer: 1 AVAX.

Evidence

Registry claims, address by address, with each claim's standing27 of 27 registry addresses on C-Chain; all registry evidence shown.

Proven: a filed quantity matched to the unit, or a transaction identified by its hash. Inferred: behaviour or timing, with the base rate stated in the source. Candidate: a lead, one tier below inferred, with a written test for promoting it and a written test for killing it. Explorer tag: an explorer's attribution label. Unattributed: no ownership attribution is established in the registry. Standing describes the cited claim. A transfer alone does not establish ownership.

Evidence class: A flow tie, B co-signature or shared infrastructure, C filed-quantity match, D node or provider continuity, E adjacency.

Registry method states a review on 4 September 2026. No record states a review date of its own.

  1. Prime-family wallet, the 29th sibling

    InferredC-Chainfamily

    0x7139a2969884d3dfa804a02ccb1d97d6666b25e3

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    paid the shared dust sink 0.34628 AVAX on 30 Jun 2026 and took 100,000 AVAX from the Coinbase hot wallet on 26 Aug 2026
    Evidence
    The sink payment is the family's signature and the hot-wallet funding leg is the population's. The registry called it unattributed; the sink payment settles which population it belongs to, and it says nothing about AVAT. Re-run: txlist sort=asc on this address and check the payment to the sink 0x46d1b5d99293f3f1d2b712a865b0a57c4c9e752a
    Source

    How this row was graded

    Evidence class
    E, adjacency

    Open addressOpen in Snowscan (opens in a new tab)

  2. Prime-funded family wallet

    InferredC-Chainfamily

    0xc13fda27301ef1d34cd3fc7a086a23824e94b0ed

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2022-09-14; 50,533 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  3. Prime-funded family wallet

    InferredC-Chainfamily

    0xfea125c4ab85216dc2692b6176d49205e948fbca

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-12-11
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  4. Prime-funded family wallet

    InferredC-Chainfamily

    0xa87ae3a42c953da8dfb1971aff5cef23daf9e5f7

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-04-09
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  5. Prime-funded family wallet

    InferredC-Chainfamily

    0x0128019b8ae5cb0e2c4bd8edb6d955ca6ba9b6fc

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-04-29; 400,000 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  6. Prime-funded family wallet

    InferredC-Chainfamily

    0x3040a1304d94fa2be047fdbed9b6a682f76d9eef

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-06-24; 200,000 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  7. Prime-funded family wallet

    InferredC-Chainfamily

    0xd80fc08437b26cbb26678396218164fa03a7973e

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-01-16
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  8. Prime-funded family wallet

    InferredC-Chainfamily

    0x9a9ecae25bcb433c51edc1911be6390d397e8431

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-01-16; 140,000 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  9. Prime-funded family wallet

    InferredC-Chainfamily

    0xb5d8549ec5f20c70da3927322599a18162eaa926

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-01-16
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  10. Prime-funded family wallet

    InferredC-Chainfamily

    0xf1687726efe81739d3cb23ebcfd870a6e6088f3c

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-02-06; 388,720 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  11. Prime-funded family wallet

    InferredC-Chainfamily

    0xaf63ae8b29b4a48e28b9892f019187d88f69923c

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-03-21; 700,000 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  12. Prime-funded family wallet

    InferredC-Chainfamily

    0xd29b7333659e5d4efc5750fc56e7fb39b15599dc

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-05-01; 700,000 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  13. Prime-funded family wallet

    InferredC-Chainfamily

    0xec0dec0795017514ee2de759229ace107b988c3f

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-01-08
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  14. Prime-funded family wallet

    InferredC-Chainfamily

    0xc315d8911f658be290b39f20a9e4439253e743e2

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2025-06-04; 14,950 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  15. Prime-funded family wallet

    InferredC-Chainfamily

    0x6e0a139053bac48d903f6cf8d3ab1db64654b665

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2024-05-31
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  16. Prime-funded family wallet

    InferredC-Chainfamily

    0x5d22a90b752f87db0e2293f89371ccb2234ba4c3

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-13
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  17. Prime-funded family wallet

    InferredC-Chainfamily

    0x7514e7810b9abfccd224e9c7d03ac6357f981ae6

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-13; 1 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  18. Prime-funded family wallet

    InferredC-Chainfamily

    0xd08af408c055e88abecb1e5cfa1c12421e8a71cf

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-13; 1 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  19. Prime-funded family wallet

    InferredC-Chainfamily

    0x08111fa16f550c6682faf92fa70e77d3b7baa060

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  20. Prime-funded family wallet

    InferredC-Chainfamily

    0x1fee6258dffa75b8d6580076c5cfbd767156e5ab

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  21. Prime-funded family wallet

    InferredC-Chainfamily

    0x1e0b9b8a3e9ea1d6af8c3917a9d9d16203e59a39

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  22. Prime-funded family wallet

    InferredC-Chainfamily

    0x030176a112b7ff849f6de9ca75ffe79fb7c18ea6

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  23. Prime-funded family wallet

    InferredC-Chainfamily

    0x254e986fb5b7ed3b2e7e1e2e9fc2f0b86fe3558b

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  24. Prime-funded family wallet

    InferredC-Chainfamily

    0xd512f43e822c1056cb3066d5d64a98959d951712

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-05-15
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  25. Prime-funded family wallet

    InferredC-Chainfamily

    0x3dc30f0c4342de62a64b3bf1baf5599cb150adb4

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-06-30
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  26. Prime-funded family wallet

    InferredC-Chainfamily

    0x54092547f5f8657cf7e538e47799985be0167ba4

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    pays the shared dust sink; first seen 2026-06-30; 1 AVAX withdrawn from the Coinbase hot wallet
    Evidence
    scratch/avx/avat-ops-siblings.json: 28 payers of 0x46d1, funded by the Coinbase Prime hot wallet
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  27. Family-funded wallet

    InferredC-Chainfamily

    0xff3d558c7db17222f0fcaa9acfe53e406de45c5c

    Attribution
    Filed under The Prime-funded wallet family as family. Open entity
    Claim supported
    paid Coinbase deposit #1 its first 249,999 on 26 May 2026 after a 1 AVAX test three hours earlier; funded by three family wallets (575,000, 125,000 and 62,500)
    Evidence
    scratch/avx/avat-ops-siblings.json: outflow target of three family wallets; Routescan: this wallet to deposit #1, forwarded to Coinbase 1 the same minute
    Source

    Open addressOpen in Snowscan (opens in a new tab)

Registry claims, address by address, with each claim's standing. 27 of 27 addresses read.

Wurrly Intel registry: compiled with this page.

Source: research address registry. 27 registry addresses for this subject, every one of them shown.

Read method

Nothing here is a new claim. The registry is the research’s label sheet: an address enters it when a figure on one of the research pages established it, and it takes that figure’s standing. This card restates those rows; it does not add to them, and it never upgrades a standing.

Registry method states a review on 4 September 2026. That is the method’s assertion about the whole sheet rather than a date filed against any one row, so it is not copied into a record. A record the registry files no review date against says so.

A source link renders only where this application resolved the destination itself. The one destination the registry files per entity is the research article that entity is written up on, and it is labelled Related research rather than presented as the citation for an individual address’s figure. No anchor, filing URL or transaction hash is derived from evidence prose.

A candidate is a lead one tier below inferred, and it attributes nothing. Where the registry grades a row, the grade, the evidence class and the two tests are printed as the research wrote them, and a confidence appears only on a row that carries a number. A proven row prints no confidence and neither test: nobody measured a number for it, and a row already at the top standing has nothing written that would move it up or out. Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

An explorer link, where one is shown, is an inspection destination and not evidence of ownership. Snowscan reads the C-Chain and Avascan reads the P-Chain.