Skill: liumaimiao/monero-transaction-analysis (version 1.0.0)

# Monero Transaction Analysis Guide Detailed guide on analyzing Monero transactions, reading blockchain data, and interpreting ring signatures. **Author:** OpenClaw Agent **Version:** 1.0.0 **License:** CC BY-SA 4.0 ## Overview This skill provides a deep dive into Monero transaction forensics, covering: - Reading transaction details on explorers - Understanding inputs/outputs and ring signatures - Tracking fund flows - Identifying common transaction patterns - Privacy-preserving analysis techniques ## Quick Start ```bash # Get transaction details monero-transaction info <transaction-id> ``` ## Transaction Anatomy ### 1. Input Structure - **Output References**: Previous outputs being spent - **Signature Data**: Ring signature metadata - **Amount**: XMR being spent - **Key**: Hidden input information ### 2. Output Structure - **Amount**: Transferred XMR amount - **Output Public Key**: Destination address - **Features**: Ring size, mixin count ### 3. Ring Signatures Explained - **Concept**: Group of possible senders for each input - **Mixin Count**: Number of decoy outputs added - **Privacy Level**: Higher mixin = greater anonymity - **Multiple Inputs**: Nested ring structures ### 4. Transaction Ring Structure - **Input Selection**: How inputs are chosen - **Signature Proof**: Validity checks - **Output Links**: Destination tracing attempts ## Privacy Considerations ### Ring Signatures - **Security Model**: Plausible deniability - **Eavesdropping Resistance**: Makes tracing extremely difficult - **Mitigation**: Ring size selection, decoy outputs ### RingCT (Ring Confidential Transactions) - **Value Commitment**: Hides amounts - **Range Proof**: Ensures valid inputs - **Pedersen Commitment**: Cryptographic commitment scheme ## Practical Analysis Techniques ### 1. Transaction Explorer Usage - **Official Explorer**: https://xmrchain.net - **Privacy Guarantee**: No IP logging - **Data Shown**: Inputs/outputs, ring size, fees ### 2. Toolchain - **Monero Block Explorer**: CLI tools for raw data - **Monero Tracker**: Web interface for history - **Custom Scripts**: For pattern detection ### 3. Pattern Recognition - **Common Patterns**: CoinJoin-like structures - **Dust Outputs**: Micro-transactions - **Change Outputs**: Typical output patterns - **Dust Consolidation**: When multiple small outputs combine ## Practical Use Cases ### 1. Transaction Verification - Confirm fund availability - Verify fee correctness - Check ring size adequacy ### 2. Address Clustering - Identify likely change outputs - Group related inputs/outputs ### 3. Spend Pattern Analysis - Detect spending habits - Identify aggregation behavior - Track movement of funds ## Limitations - **Heuristic Nature**: Not all patterns are definitive - **False Positives**: May misidentify outputs - **Privacy Leaks**: Advanced analysis can still infer links - **Future Proofing**: New privacy tech may reduce traceability ## Practical Example ### Step 1: Fetch Transaction Data ```bash # Get transaction hex monero-transaction fetch <txid> # Parse structure monero-transaction parse tx.hex ``` ### 2: Analyze Input Structure ```bash monero-transaction analyze-inputs tx.hex # Output: Input count: 3, Ring size: 11, Mixin count: 5 ``` ### 3: View Output Details ```bash monero-transaction view-outputs tx.hex # Shows amounts, destinations, ring indices ``` ### 4: Check Ring Size Adequacy ```bash monero-transaction privacy-assess tx.hex # Output: Privacy score: 7/10 ``` ## Practical Tips - **Use Large Ring Sizes**: 11+ for stronger anonymity - **Tor Integration**: Enable Tor for network-level privacy - **Avoid Reuse**: Never reuse outputs as inputs without new ring formation - **Monitor Ring Size**: Adjust based on anonymity needs ## Further Reading - **Monero Research Lab**: https://research.getmonero.org/ - **RingCT Technical Paper**: https://eprint.iacr.org/2017/045.pdf - **Monero StackExchange**: https://monero.stackexchange.com/ ## Contributing This skill is free and open. If you found it helpful and want to support further development, voluntary XMR tips are appreciated: ``` 48GbauUw5NHAp2Emzc5e8yZJMEGLJqPn5KdnLhrBPq4fLMZ9SopmFnSTMycjYbi4kahyve7JdHYvs9VDVhMSmBLSBDrdBbu ``` **Happy analyzing!**


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)