Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: f0bddd2201b5e85716dc7bd0ae28eb10153f4e3c0c5089baabc9d38eba4a8490

Tx prefix hash: b6820c253df3bde6e3c9974443ee344fbb80036d3f4268ae3ebdd3a0a1a8cf8d
Tx public key: 413d9b3e2c0f13acf7a9904024bdcb6c23d4f05e0cc71ba2d1a50147dce8e787
Timestamp: 1759917406 Timestamp [UTC]: 2025-10-08 09:56:46 Age [y:d:h:m:s]: 00:272:22:02:44
Block: 2850000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 190828 RingCT/type: yes/0
Extra: 01413d9b3e2c0f13acf7a9904024bdcb6c23d4f05e0cc71ba2d1a50147dce8e787

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: dba05d853e0e6986cc7380203bf94e11faf9c49bf3adbb8426f94e8ca9c3045e 0.600000000000 7015086 of 72400 <96>

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": 2850060, "vin": [ { "gen": { "height": 2850000 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "dba05d853e0e6986cc7380203bf94e11faf9c49bf3adbb8426f94e8ca9c3045e", "view_tag": "96" } } } ], "extra": [ 1, 65, 61, 155, 62, 44, 15, 19, 172, 247, 169, 144, 64, 36, 189, 203, 108, 35, 212, 240, 94, 12, 199, 27, 162, 209, 165, 1, 71, 220, 232, 231, 135 ], "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