Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 656573774a10e8df2baa9a463b33870adfea5c657dc14e8686fca475549b29f4

Tx prefix hash: 345c0dbd5908de1f6cb2e5f4c74df20b37b08f79219cb6f1a42ecdf7c99c931a
Tx public key: ce77d0062e14070dfb42b534fdb5e4dd47e4c2783a6ad8c711e4ca8e3595fa72
Timestamp: 1755624347 Timestamp [UTC]: 2025-08-19 17:25:47 Age [y:d:h:m:s]: 00:329:19:28:32
Block: 2815048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 230589 RingCT/type: yes/0
Extra: 01ce77d0062e14070dfb42b534fdb5e4dd47e4c2783a6ad8c711e4ca8e3595fa72

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 53d605a0bcc048cb0c9cc3cc6835b402a1d196837c26d3e4b9871992102f21a0 0.600000000000 6957655 of 72400 <e5>

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": 2815108, "vin": [ { "gen": { "height": 2815048 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "53d605a0bcc048cb0c9cc3cc6835b402a1d196837c26d3e4b9871992102f21a0", "view_tag": "e5" } } } ], "extra": [ 1, 206, 119, 208, 6, 46, 20, 7, 13, 251, 66, 181, 52, 253, 181, 228, 221, 71, 228, 194, 120, 58, 106, 216, 199, 17, 228, 202, 142, 53, 149, 250, 114 ], "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