trenchcoat
Free · no sign-up
Website report · 2 h ago

payoutholders.xyz

“PayoutHolders: holders get the fees, sellers pay”

Template-written 13 evidence items Code reader analysed 11 scripts
What this means for you

PayoutHolders talked to 1 outside service on a first visit.E6

  • What loads is a page only: no calls to its own backend, no wallet code, no contract calls, no AI services and no live connections.E12
  • We saw no known analytics or advertising services load on the first visit.E1

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).

Calls its own backend none seen
Wallet code none seen
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What loads is a page only: no own backend calls, wallet code, contract calls, AI services or live connections.E12

What it is

  • The Internet Archive has never saved this site, so it is probably new.E13
  • The site describes itself as: “Hold $PAYOUT and get SOL every 5 minutes. Creator fees and the treasury are paid to holders, weighted by time held. Sellers forfeit their va”E2
  • It's built with Next.js and React (common tools for building web apps).E7E8
  • In your browser it can copy text to your clipboard.E9
  • It has sections such as /coins, /rounds, /docs, /verify, /status and /launch.E11

Where your data goes

Not identifiedServices we don't have in our list yet. 1
olive-accused-cardinal-331.mypinata.cloudnot identified 2×E6

Pages and API calls

Pages it links to

//coins/rounds/docs/verify/status/launch/wallet/changes/terms/privacy

Endpoints

Called while loading (seen) or named in the code (code).

/api/statecodeE10

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

E1
Page title: PayoutHolders: holders get the fees, sellers pay
page title · https://payoutholders.xyz/
E2
Page description: Hold $PAYOUT and get SOL every 5 minutes. Creator fees and the treasury are paid to holders, weighted by time held. Sellers forfeit their vault to the
page description · https://payoutholders.xyz/
E3
Site name: PayoutHolders
page site_name · https://payoutholders.xyz/
E4
Main heading: Sellers pay. Holders get paid.
page h1 · https://payoutholders.xyz/
E5
56 request(s) to payoutholders.xyz
types: 41 fetch, 8 script, 3 image
GET https://payoutholders.xyz/ · fetch · 56 requests · network recording
E6
2 request(s) to olive-accused-cardinal-331.mypinata.cloud
types: 2 image
GET https://olive-accused-cardinal-331.mypinata.cloud/ipfs/QmTVDGWPJN7q7dqg6eM5NnFMF167GJkrfVfKzvqB71RUJ1 · image · 2 requests · network recording
E7
Next.js detected by the code reader (next-runtime)
confidence: high
payoutholders.xyz/_next/static/immutable/chunks/turbopack-3h_ctkfaeun7f.js · “next-runtime” · the code reader
E8
React detected by the code reader (react-runtime)
confidence: medium
payoutholders.xyz/_next/static/immutable/chunks/1b1-wny-6sd-l.js · “react-runtime” · the code reader
E9
Uses the browser ability: clipboard_write
can copy text to your clipboard
payoutholders.xyz/_next/static/immutable/chunks/16ol-pf8y4_o0.js @ 1:22539 · “clipboard.writeText(” · pattern scan
E10
Code reader found the endpoint /api/state
how: call:fetch
payoutholders.xyz/_next/static/immutable/chunks/16ol-pf8y4_o0.js @ 1:10197 · “/api/state” · the code reader
E11
30 links to pages on the same site
page links · https://payoutholders.xyz/ · /, /coins, /rounds, /docs, /verify, /status, /launch, /wallet, /changes, /terms, /privacy
E12
58 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://payoutholders.xyz/ · summary · 58 requests · network recording
E13
The Internet Archive has no saved copy of payoutholders.xyz
page web archive · https://web.archive.org/web/*/payoutholders.xyz

Limits

  • We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
  • Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
  • Some trackers only load after you accept cookies or log in, so the real list can be longer.
  • We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
  • This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
  • The code reader hit its size budget on parts of 3 large bundle file(s); those parts weren't fully analysed.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id EkoxTDoI.