Tx hash: 517a04b11a5b341455d961914df37ba31230a97d3a34c148adb9b3292ce667ad
Tx prefix hash: 092da1b19082a97446e169ed7c93658bcb888ad0b81d46f6231464477a5d64c0
Tx public key: 039498d4e979f23529b07961c690f2f59e1515801c1bdff9e003365cef4ca9d2
| Timestamp: 1780104515 | Timestamp [UTC]: 2026-05-30 01:28:35 | Age [y:d:h:m:s]: 00:000:15:53:05 |
| Block: 2973 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 472 | RingCT/type: yes/0 |
| Extra: 01039498d4e979f23529b07961c690f2f59e1515801c1bdff9e003365cef4ca9d2 | ||
1 output(s) for total of 34.979215938679 xmr
| stealth address | amount | amount idx | tag |
| 00: 7e5d2ab0bebf0287dbcbcc5b025e13f0998f7dc23f32a50f84a28654ba525798 | 34.979215938679 | 2961 of 0 | - |
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": 3033,
"vin": [ {
"gen": {
"height": 2973
}
}
],
"vout": [ {
"amount": 34979215938679,
"target": {
"key": "7e5d2ab0bebf0287dbcbcc5b025e13f0998f7dc23f32a50f84a28654ba525798"
}
}
],
"extra": [ 1, 3, 148, 152, 212, 233, 121, 242, 53, 41, 176, 121, 97, 198, 144, 242, 245, 158, 21, 21, 128, 28, 27, 223, 249, 224, 3, 54, 92, 239, 76, 169, 210
],
"rct_signatures": {
"type": 0
}
}