Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 97a0c34f1478fcff7b404d75ffebfc8350e224bf680d5d6c6e7cb5f19f467801

Tx prefix hash: 2575b6161f4878576a954837c71a88965845c93f9cd1ce9f08ba68e5d2e663c8
Tx public key: 5d75f60aa3b543704022d38d6af7ef63725edac9f49a0979db2a2a01edb05c24
Timestamp: 1774150576 Timestamp [UTC]: 2026-03-22 03:36:16 Age [y:d:h:m:s]: 00:113:20:32:21
Block: 2965493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 79527 RingCT/type: yes/0
Extra: 015d75f60aa3b543704022d38d6af7ef63725edac9f49a0979db2a2a01edb05c2402080000000100000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: eb9df627dd71ba0cc80966dd7eb82e85b8c5ce74b6dad7a0d3e01c9537f7d57a 0.600000000000 7139666 of 72400 <81>

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": 2965553, "vin": [ { "gen": { "height": 2965493 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "eb9df627dd71ba0cc80966dd7eb82e85b8c5ce74b6dad7a0d3e01c9537f7d57a", "view_tag": "81" } } } ], "extra": [ 1, 93, 117, 246, 10, 163, 181, 67, 112, 64, 34, 211, 141, 106, 247, 239, 99, 114, 94, 218, 201, 244, 154, 9, 121, 219, 42, 42, 1, 237, 176, 92, 36, 2, 8, 0, 0, 0, 1, 0, 0, 0, 0 ], "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