Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 7cd27091a41cb6f191751436759d78d44addc87bd0cde005e32cb4b4769bc33b

Tx prefix hash: 29ded69d03ebbe1afd34b3b2d4aeb4721785548b028b25c98e9c73c08e968df3
Tx public key: 6f309fe22749b84a9d0e870608fe1d157a9fd52b3f96f08e9b26b0a0d71e10d2
Timestamp: 1779399761 Timestamp [UTC]: 2026-05-21 21:42:41 Age [y:d:h:m:s]: 00:047:12:06:44
Block: 3007388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 33499 RingCT/type: yes/0
Extra: 016f309fe22749b84a9d0e870608fe1d157a9fd52b3f96f08e9b26b0a0d71e10d2

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: f5f3765a85b08e0c440379060e69a6b07f758c7a70f1eabb7fff08f6d46da504 0.600000000000 7185609 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": 3007448, "vin": [ { "gen": { "height": 3007388 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "f5f3765a85b08e0c440379060e69a6b07f758c7a70f1eabb7fff08f6d46da504", "view_tag": "72" } } } ], "extra": [ 1, 111, 48, 159, 226, 39, 73, 184, 74, 157, 14, 135, 6, 8, 254, 29, 21, 122, 159, 213, 43, 63, 150, 240, 142, 155, 38, 176, 160, 215, 30, 16, 210 ], "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