Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: bbeaa603bca19ec40fc334ffdd06de6c727e51be6871ce9739becb945cb73ac4

Tx prefix hash: b7f3b519c475ad6d68ef4123e0c782284818008df1a2f6c3510926006b927a56
Tx public key: b9360d584a5a8df143047ccbd927f9fdbced8560ecc3cfa0a2e174d5cc482a07
Timestamp: 1761842260 Timestamp [UTC]: 2025-10-30 16:37:40 Age [y:d:h:m:s]: 00:248:14:43:36
Block: 2865283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 174089 RingCT/type: yes/0
Extra: 01b9360d584a5a8df143047ccbd927f9fdbced8560ecc3cfa0a2e174d5cc482a0702085ca56e816b9a2b9a

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 240a862359204ad65b45bef36864470f9808abe5aad5c0f72cf05e805255d56c 0.600000000000 7034729 of 72400 <86>

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": 2865343, "vin": [ { "gen": { "height": 2865283 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "240a862359204ad65b45bef36864470f9808abe5aad5c0f72cf05e805255d56c", "view_tag": "86" } } } ], "extra": [ 1, 185, 54, 13, 88, 74, 90, 141, 241, 67, 4, 124, 203, 217, 39, 249, 253, 188, 237, 133, 96, 236, 195, 207, 160, 162, 225, 116, 213, 204, 72, 42, 7, 2, 8, 92, 165, 110, 129, 107, 154, 43, 154 ], "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