Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 8a9bd4437b05e0815ad2f0b2005f9784b1ead605ca65c7a47c65e60bcfd52090

Tx prefix hash: edfe95f0fe753d17504cdd49c52d4b2a2e34988c0391ec93a4da9751986f54c8
Tx public key: d94743f714aee2e9b07f72fc0d6d93061a5add911713d59f53b8b6404e0ac8f4
Timestamp: 1765575709 Timestamp [UTC]: 2025-12-12 21:41:49 Age [y:d:h:m:s]: 00:208:14:29:39
Block: 2895671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 146038 RingCT/type: yes/0
Extra: 01d94743f714aee2e9b07f72fc0d6d93061a5add911713d59f53b8b6404e0ac8f4

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: e04278c0c0b3555e4533ea532fe8d1c2fa7c559b697f84c552a3d670fec791fc 0.600000000000 7066353 of 72400 <b3>

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": 2895731, "vin": [ { "gen": { "height": 2895671 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "e04278c0c0b3555e4533ea532fe8d1c2fa7c559b697f84c552a3d670fec791fc", "view_tag": "b3" } } } ], "extra": [ 1, 217, 71, 67, 247, 20, 174, 226, 233, 176, 127, 114, 252, 13, 109, 147, 6, 26, 90, 221, 145, 23, 19, 213, 159, 83, 184, 182, 64, 78, 10, 200, 244 ], "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