Monero Testnet Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 53169a3a9e51fb7638c7be5d7cb8600fef68153edc495af3a19f93b4cf01de2a

Tx prefix hash: 641ed1ea2c44952b4300b9644f4297ad679e78938aceebd7ed5beda34361d667
Tx public key: 4df83f985b5c7aa314396b674d4421bc8e4a0ba656d7d5cfd91848c0721fd482
Timestamp: 1753184406 Timestamp [UTC]: 2025-07-22 11:40:06 Age [y:d:h:m:s]: 00:358:12:54:14
Block: 2795847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 250081 RingCT/type: yes/0
Extra: 014df83f985b5c7aa314396b674d4421bc8e4a0ba656d7d5cfd91848c0721fd4820208bfa3a159063e792c

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 220a3ee49fe042b4d8323e4afdba78b8410bb856465a60e44f61b7e8ff857921 0.600000000000 6937731 of 72400 <72>

Check which outputs belong to given Monero address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Monero in this transaction

Tx private key can be obtained using get_tx_key command in monero-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 2795907, "vin": [ { "gen": { "height": 2795847 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "220a3ee49fe042b4d8323e4afdba78b8410bb856465a60e44f61b7e8ff857921", "view_tag": "72" } } } ], "extra": [ 1, 77, 248, 63, 152, 91, 92, 122, 163, 20, 57, 107, 103, 77, 68, 33, 188, 142, 74, 11, 166, 86, 215, 213, 207, 217, 24, 72, 192, 114, 31, 212, 130, 2, 8, 191, 163, 161, 89, 6, 62, 121, 44 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2026-05-17-bfa342e (1.3) | monero version: 0.18.4.0-release