Node status
Watch
Menu

Spam detector

Light traffic · checks running
9 transactions checked#4197085

Transaction pace

Block #4197080 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.Block #4197081 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.Block #4197082 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.Block #4197083 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.Block #4197084 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.Block #4197085 · Ordinary transactions confirmed together in this block. · Comparing blocks reveals bursts of transaction activity.

Collecting comparison

0.5Transactions / block
—Usual / block
3Ordinary transactions
#4197080 – #4197085 · 6 blocks

Repeated structure

Transaction structure · The transaction version and its mix of inputs, outputs and shielded actions. · Comparing these shapes reveals recurring transaction patterns.Matching structure groups · Each color groups transactions with the same public structure. · A growing dominant color highlights a repeated pattern.

Light traffic

33.33%Largest matching group
—Same pattern before
3Distinct structures
#4197080 – #4197085 · 6 blocks

Fee efficiency

Transaction fees · Fees paid for transactions included in blocks. · Relating fees to activity shows the cost of adding network load.Public actions · A shared measure of public transaction activity. · Lets the fees of small and large transactions be compared on the same basis.Usual fee per action · The median fee per action in comparable earlier blocks. · Provides a baseline for spotting unusually cheap activity.Current fee per action · Recent transaction fees divided by their public action count. · A lower value means more activity for each unit of fee.

Light traffic

1,428.57zat / action
—Usual zat / action
3Transactions with fees
#4197080 – #4197085 · 6 blocks

Proof reuse

Sapling proofs · Cryptographic proofs supporting private Sapling transfers. · They let nodes check shielded activity while preserving privacy.Proof uniqueness check · Compares Sapling proof bytes within each transaction. · Detects the exact proof-copying pattern seen in historical spam.Unique proofs · Proofs with distinct bytes within their transaction. · This is the expected outcome of the proof-reuse check.Reused proofs · Identical Sapling proof bytes repeated within a transaction. · This is the signature behind the historical proof-reuse spam waves.

No reuse found

2Proofs checked
0Extra copies
0Blocked deliveries
— historical matches
#4197080 – #4197085 · 6 blocksBlocked: retained native events

Transaction history

—

Awaiting classified transaction history

Spam history

0.00% inspected

Confirmed proof reuse

0 of 0 events
Block One transaction Identical proof bytes
0extra proof copies recorded

0 transactions · 0 blocks

No proof reuse in checked history

1

Possible transaction flooding

0 recorded phases
Detection rule

32+ Sapling outputs · at least 50% of P2P txs · sustained across blocks

At least 360 large-output txs across 360 blocks, over 4–12 hours. Four of six consecutive 60-block groups must qualify: at least 20 large-output txs, half of P2P txs, and 12 majority-large blocks representing at least half of P2P-bearing blocks. The full window must also meet both 50% shares.

Matching stretches join across gaps of at most 360 blocks and six hours. Quieter high-output traffic alone does not qualify.

Blocks with confirmed proof reuse are excluded from flooding counts and contributing blocks. All 360 heights remain in the time window. Charts show total P2P activity for context. A structural pattern, not proof of intent.

Checking historical blocks

1
Pirate Chain

MareLiberum

Network status

Download bootstrap

This bootstrap includes all four query indexes.

txindex
Look up transactions by transaction ID.
addressindex
Query transparent address balances and history.
spentindex
Find which transaction spent a transparent output.
timestampindex
Find blocks within a timestamp range.

The indexes use extra disk space and add work when new blocks are indexed.

If you do not need these extra indexes, choose the official CryptoForge bootstrap.

Continue with this bootstrapDownload official bootstrap