Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 3d63ae5e80c7eb22d8043b822782826f2d82721cfc8f755a44dd87c343f9632e

Tx prefix hash: f36f6c66a3077ddeac3c08d7c5fb01bf746778d1f063c44d9a62fe8a0c80d6e5
Tx public key: 749dfdff4f5adc10cfc588304d85e176977a950fabcdf39d5de133413446b84f
Timestamp: 1761242953 Timestamp [UTC]: 2025-10-23 18:09:13 Age [y:d:h:m:s]: 00:262:00:55:21
Block: 2860741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 183270 RingCT/type: yes/0
Extra: 01749dfdff4f5adc10cfc588304d85e176977a950fabcdf39d5de133413446b84f0208e8f998834e248a3d

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: f855f46659063e7db15124e48359ad30d3fccb423e07d7aa72cc2cfd4710b6f6 0.600000000000 7026177 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": 2860801, "vin": [ { "gen": { "height": 2860741 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "f855f46659063e7db15124e48359ad30d3fccb423e07d7aa72cc2cfd4710b6f6", "view_tag": "63" } } } ], "extra": [ 1, 116, 157, 253, 255, 79, 90, 220, 16, 207, 197, 136, 48, 77, 133, 225, 118, 151, 122, 149, 15, 171, 205, 243, 157, 93, 225, 51, 65, 52, 70, 184, 79, 2, 8, 232, 249, 152, 131, 78, 36, 138, 61 ], "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