Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: de73e2a303520858a5b07c7c0decfabf0f37882e588e15bede6b40b224123495

Tx prefix hash: 04416f19abfab06304e8ec7e814741c29dcdc0bcb78a06a896431a229eebd731
Tx public key: 8d9a3e9b1b424bce2ccbc1e7e2f5ea85449a8223bfecf7d7f14350af1d4dc1da
Timestamp: 1783246670 Timestamp [UTC]: 2026-07-05 10:17:50 Age [y:d:h:m:s]: 00:024:14:35:04
Block: 3038741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 17209 RingCT/type: yes/0
Extra: 018d9a3e9b1b424bce2ccbc1e7e2f5ea85449a8223bfecf7d7f14350af1d4dc1da

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 0c22cfbfe1a53274e36b5e4ec2df4bbbc21a7891008b375b60db566d52cb4b24 0.600000000000 7345287 of 72400 <59>

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": 3038801, "vin": [ { "gen": { "height": 3038741 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "0c22cfbfe1a53274e36b5e4ec2df4bbbc21a7891008b375b60db566d52cb4b24", "view_tag": "59" } } } ], "extra": [ 1, 141, 154, 62, 155, 27, 66, 75, 206, 44, 203, 193, 231, 226, 245, 234, 133, 68, 154, 130, 35, 191, 236, 247, 215, 241, 67, 80, 175, 29, 77, 193, 218 ], "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