Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 6aaf10904fa9f50dbd8280916744cfc8a9eb7866ee7007619b157cb3ec9f7188

Tx prefix hash: c98315ef209d3310a0290e83ec4546d077ebfd539b0fca1847cec136851bb9d0
Tx public key: 3ab3a823d5cad71cc183c9a2654df0d699d617d5f9dac2d4228a32f1f0b4e8cc
Timestamp: 1775904328 Timestamp [UTC]: 2026-04-11 10:45:28 Age [y:d:h:m:s]: 00:087:18:57:58
Block: 2979384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 61375 RingCT/type: yes/0
Extra: 013ab3a823d5cad71cc183c9a2654df0d699d617d5f9dac2d4228a32f1f0b4e8cc

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 592ef69e66da6f8d6fd8be4c31c8efaf1e9eb611795d058d264063ca24660254 0.600000000000 7153814 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": 2979444, "vin": [ { "gen": { "height": 2979384 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "592ef69e66da6f8d6fd8be4c31c8efaf1e9eb611795d058d264063ca24660254", "view_tag": "84" } } } ], "extra": [ 1, 58, 179, 168, 35, 213, 202, 215, 28, 193, 131, 201, 162, 101, 77, 240, 214, 153, 214, 23, 213, 249, 218, 194, 212, 34, 138, 50, 241, 240, 180, 232, 204 ], "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