Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 4e0e57a23653739eb893b3a88d1fd05c375038aca3e7c90fe80f017fbfea272c

Tx prefix hash: e43754c91800100eff34dbc9da56cc03d3204acb700d7a3eb0e45b9a2e64b903
Tx public key: 1b74cd142dbfa1f7d4cad7194c10fb0f17e60701fd5e3fcf64a31c6d950422cd
Timestamp: 1776248855 Timestamp [UTC]: 2026-04-15 10:27:35 Age [y:d:h:m:s]: 00:095:22:07:56
Block: 2982371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 66593 RingCT/type: yes/0
Extra: 011b74cd142dbfa1f7d4cad7194c10fb0f17e60701fd5e3fcf64a31c6d950422cd02080000000100000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: f81aa2a0a8ced38c0aa8f7cce64fce073e45728d3998284d06035cc8c71d3106 0.600000000000 7157177 of 72400 <64>

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": 2982431, "vin": [ { "gen": { "height": 2982371 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "f81aa2a0a8ced38c0aa8f7cce64fce073e45728d3998284d06035cc8c71d3106", "view_tag": "64" } } } ], "extra": [ 1, 27, 116, 205, 20, 45, 191, 161, 247, 212, 202, 215, 25, 76, 16, 251, 15, 23, 230, 7, 1, 253, 94, 63, 207, 100, 163, 28, 109, 149, 4, 34, 205, 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