Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 98f7b4013b33ea246fb740a74ade1b2f553b7d45474d7cea6b0e8ce80a56e7a9

Tx prefix hash: d793bb48d7333827b28d804c187342bed5cb88cf2eb94a9aee1eee801f62ac98
Tx public key: 51a3b951e977f705d0e3f849019600ddd902814d71b6a3d334d6bb6cee7d11ec
Timestamp: 1777945429 Timestamp [UTC]: 2026-05-05 01:43:49 Age [y:d:h:m:s]: 00:069:12:28:48
Block: 2995948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 48772 RingCT/type: yes/0
Extra: 0151a3b951e977f705d0e3f849019600ddd902814d71b6a3d334d6bb6cee7d11ec02080000000100000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: e70d87b51a01c7f8ba1b0887439a50ed8e50a6bc0bfaab66a5613a4941d3bcb9 0.600000000000 7172819 of 72400 <84>

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": 2996008, "vin": [ { "gen": { "height": 2995948 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "e70d87b51a01c7f8ba1b0887439a50ed8e50a6bc0bfaab66a5613a4941d3bcb9", "view_tag": "84" } } } ], "extra": [ 1, 81, 163, 185, 81, 233, 119, 247, 5, 208, 227, 248, 73, 1, 150, 0, 221, 217, 2, 129, 77, 113, 182, 163, 211, 52, 214, 187, 108, 238, 125, 17, 236, 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