Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 47f241c34519d48bdc52f2bc05cebcddcfc0ab72f42bef0f86f7b4da6ec57200

Tx prefix hash: 41a16f6a9d0f0ce543fa248a375597581ad81417bc9c313634cd9f0e2b15aa01
Tx public key: 24d9d4d8a71bf3868bab9e47291b1eff1ef19e5ddb686c374ae8674c816d85cb
Timestamp: 1777373938 Timestamp [UTC]: 2026-04-28 10:58:58 Age [y:d:h:m:s]: 00:055:16:45:57
Block: 2991136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 38933 RingCT/type: yes/0
Extra: 0124d9d4d8a71bf3868bab9e47291b1eff1ef19e5ddb686c374ae8674c816d85cb02080000000200000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 2b5d5a7d6b2898fe6f39024a280d4f6e1ac7bd791c7c2dd85a1758572c574040 0.600000000000 7166614 of 72400 <63>

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": 2991196, "vin": [ { "gen": { "height": 2991136 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "2b5d5a7d6b2898fe6f39024a280d4f6e1ac7bd791c7c2dd85a1758572c574040", "view_tag": "63" } } } ], "extra": [ 1, 36, 217, 212, 216, 167, 27, 243, 134, 139, 171, 158, 71, 41, 27, 30, 255, 30, 241, 158, 93, 219, 104, 108, 55, 74, 232, 103, 76, 129, 109, 133, 203, 2, 8, 0, 0, 0, 2, 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