Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 7f0ce095283d348317441310951a55262b0392fb4b2f6dff55ff438d77254e62

Tx prefix hash: 888d2849486c64b8b9aaf8916e377251cf6bd6e4e09e29a2cfb48d7c91f38ba3
Tx public key: 9b7ee46fc6afe54257a55d067db445fbb471916314627c1a0f76d5c7a2ae5c91
Timestamp: 1758831217 Timestamp [UTC]: 2025-09-25 20:13:37 Age [y:d:h:m:s]: 00:287:09:25:51
Block: 2841670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 200558 RingCT/type: yes/0
Extra: 019b7ee46fc6afe54257a55d067db445fbb471916314627c1a0f76d5c7a2ae5c91020842b7881c844583b8

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 30fe161686b0f62831c3eeea34150d77391c4d827a45710d54ec38868c1ea297 0.600000000000 7006101 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": 2841730, "vin": [ { "gen": { "height": 2841670 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "30fe161686b0f62831c3eeea34150d77391c4d827a45710d54ec38868c1ea297", "view_tag": "64" } } } ], "extra": [ 1, 155, 126, 228, 111, 198, 175, 229, 66, 87, 165, 93, 6, 125, 180, 69, 251, 180, 113, 145, 99, 20, 98, 124, 26, 15, 118, 213, 199, 162, 174, 92, 145, 2, 8, 66, 183, 136, 28, 132, 69, 131, 184 ], "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