Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: d8dd737b0f26dbec795e8a344d5a82cecbef693321f087644a6e2bc764e67010

Tx prefix hash: 0ef358bea62adce31afea45c431c91b963144acc9eeaf4a4de927798d6135971
Tx public key: 3454fece98ee0fa1d413a8a4f6e80c0da9ee2493068df0e280528bbaa06474d2
Timestamp: 1711192569 Timestamp [UTC]: 2024-03-23 11:16:09 Age [y:d:h:m:s]: 02:116:01:45:16
Block: 2459531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 587476 RingCT/type: yes/0
Extra: 013454fece98ee0fa1d413a8a4f6e80c0da9ee2493068df0e280528bbaa06474d2020874a765bbd412611e

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 53304d528a48ec3fe9d5a6c00a557276ce1e321fee420cb6929df0fe9c3a3417 0.600000000000 6372749 of 72400 <c2>

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": 2459591, "vin": [ { "gen": { "height": 2459531 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "53304d528a48ec3fe9d5a6c00a557276ce1e321fee420cb6929df0fe9c3a3417", "view_tag": "c2" } } } ], "extra": [ 1, 52, 84, 254, 206, 152, 238, 15, 161, 212, 19, 168, 164, 246, 232, 12, 13, 169, 238, 36, 147, 6, 141, 240, 226, 128, 82, 139, 186, 160, 100, 116, 210, 2, 8, 116, 167, 101, 187, 212, 18, 97, 30 ], "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