Monero Testnet Explorer

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

Autorefresh is OFF

Tx hash: 09a617ff5822d3600da021ca3f6b646eebc7105efcbc417f3ce447e85d365b83

Tx prefix hash: cc30d5f3398cb24cc65452e506687b4b954bfd3c159289a1c401d1a13a6deb07
Tx public key: 79603bc7f2f13e3837d14b417a39bc247292f5d33fb007e434fff2365ab4a645
Timestamp: 1777651193 Timestamp [UTC]: 2026-05-01 15:59:53 Age [y:d:h:m:s]: 00:063:17:27:22
Block: 2993526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0947 kB
Tx version: 2 No of confirmations: 44475 RingCT/type: yes/0
Extra: 0179603bc7f2f13e3837d14b417a39bc247292f5d33fb007e434fff2365ab4a64502080000000100000000

1 output(s) for total of 0.600000000000 xmr

stealth address amount amount idx tag
00: fef44d9ee0921d217394fb111d96aafe105d3a3a34ba2e8b4e3a1c06b8a52d1d 0.600000000000 7169160 of 72400 <e1>

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": 2993586, "vin": [ { "gen": { "height": 2993526 } } ], "vout": [ { "amount": 600000000000, "target": { "tagged_key": { "key": "fef44d9ee0921d217394fb111d96aafe105d3a3a34ba2e8b4e3a1c06b8a52d1d", "view_tag": "e1" } } } ], "extra": [ 1, 121, 96, 59, 199, 242, 241, 62, 56, 55, 209, 75, 65, 122, 57, 188, 36, 114, 146, 245, 211, 63, 176, 7, 228, 52, 255, 242, 54, 90, 180, 166, 69, 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