Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: f0dc6775b48444229223629d3dee032c6d920a2c5d4c134a73f51957e982d03f

Tx prefix hash: 406dc14bc83f5c19d469ed129e19eea4fd23ec7beefa3a584661ed1a378e6c1e
Tx public key: c3facfd9cc0c72b119299a8ee0e2b0bf604dbe437783dad2f4c5d1d3b21d1b23
Timestamp: 1727104990 Timestamp [UTC]: 2024-09-23 15:23:10 Age [y:d:h:m:s]: 01:292:16:39:28
Block: 2588717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 455647 RingCT/type: yes/0
Extra: 01c3facfd9cc0c72b119299a8ee0e2b0bf604dbe437783dad2f4c5d1d3b21d1b23

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: fac0d166e7662115bcb5d91c412ac3c8e0d40d419d3d8716197504a1616bd8b7 0.600000000000 6522246 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": 2588777, "vin": [ { "gen": { "height": 2588717 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "fac0d166e7662115bcb5d91c412ac3c8e0d40d419d3d8716197504a1616bd8b7", "view_tag": "96" } } } ], "extra": [ 1, 195, 250, 207, 217, 204, 12, 114, 177, 25, 41, 154, 142, 224, 226, 176, 191, 96, 77, 190, 67, 119, 131, 218, 210, 244, 197, 209, 211, 178, 29, 27, 35 ], "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