Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: efd85ee09120eefb77847a3560225c3d7cc8a6aecb203c8efb58f6cb8fe3311b

Tx prefix hash: 858e839a214570ddd663c1ad9cee45a79664eff13654a97745eae52a5fbd8302
Tx public key: fc77cf4cd6c58a4f02b30d33b52fbf0e152e35d58e4aac1cb68befc90c95e6d0
Timestamp: 1735644948 Timestamp [UTC]: 2024-12-31 11:35:48 Age [y:d:h:m:s]: 01:185:02:21:21
Block: 2658788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0850 kB
Tx version: 2 No of confirmations: 379343 RingCT/type: yes/0
Extra: 01fc77cf4cd6c58a4f02b30d33b52fbf0e152e35d58e4aac1cb68befc90c95e6d0

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: 0f3c0afbe5a11a2c970c46dfb22344b41c087a847c3958e0c420e2e820e74301 0.600000000000 6686067 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": 2658848, "vin": [ { "gen": { "height": 2658788 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "0f3c0afbe5a11a2c970c46dfb22344b41c087a847c3958e0c420e2e820e74301", "view_tag": "80" } } } ], "extra": [ 1, 252, 119, 207, 76, 214, 197, 138, 79, 2, 179, 13, 51, 181, 47, 191, 14, 21, 46, 53, 213, 142, 74, 172, 28, 182, 139, 239, 201, 12, 149, 230, 208 ], "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