Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: e986ca1c3dd7194e14fdd48d3ce331095f1eb72c7d21b1dcaa87c1de40b7992d

Tx prefix hash: 12f6f2989a4bc93f910797e679ad078c8aa38735ea389c9a49df41678393e1a6
Tx public key: 7eec0c8748b3f952b780e269654ca7d15b517348093c6f1eaff7859a9edb545e
Timestamp: 1774950841 Timestamp [UTC]: 2026-03-31 09:54:01 Age [y:d:h:m:s]: 00:098:12:13:21
Block: 2971985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 68547 RingCT/type: yes/0
Extra: 017eec0c8748b3f952b780e269654ca7d15b517348093c6f1eaff7859a9edb545e02080000000100000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: df620784111c67e5f8b039c8232385d6e100d832b7b8b76d6aa922187547dbd9 0.600000000000 7146281 of 72400 <80>

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": 2972045, "vin": [ { "gen": { "height": 2971985 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "df620784111c67e5f8b039c8232385d6e100d832b7b8b76d6aa922187547dbd9", "view_tag": "80" } } } ], "extra": [ 1, 126, 236, 12, 135, 72, 179, 249, 82, 183, 128, 226, 105, 101, 76, 167, 209, 91, 81, 115, 72, 9, 60, 111, 30, 175, 247, 133, 154, 158, 219, 84, 94, 2, 8, 0, 0, 0, 1, 0, 0, 0, 0 ], "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