Tx hash: 730136ec6c54e94cbfbc055f722d69751cc83a74a943fe6d20eb4b63a2f7920a
Tx prefix hash: 950317b58ad066809f717cf9a8781c30c0ac28604b48513eabc4ffde81505ee8
Tx public key: 62c171e0b32b53d7051e3fd6048a95543995de9e69f1ea178b12291977b6fe2d
| Timestamp: 1779995394 | Timestamp [UTC]: 2026-05-28 19:09:54 | Age [y:d:h:m:s]: 00:004:04:19:50 |
| Block: 2054 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 1491 | RingCT/type: yes/0 |
| Extra: 0162c171e0b32b53d7051e3fd6048a95543995de9e69f1ea178b12291977b6fe2d | ||
1 output(s) for total of 35.040583202761 xmr
| stealth address | amount | amount idx | tag |
| 00: b5bc037533973e9b70a8afde54443964ec4e30a60d03295d69e5fb4d9813460e | 35.040583202761 | 2042 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": 2114,
"vin": [ {
"gen": {
"height": 2054
}
}
],
"vout": [ {
"amount": 35040583202761,
"target": {
"key": "b5bc037533973e9b70a8afde54443964ec4e30a60d03295d69e5fb4d9813460e"
}
}
],
"extra": [ 1, 98, 193, 113, 224, 179, 43, 83, 215, 5, 30, 63, 214, 4, 138, 149, 84, 57, 149, 222, 158, 105, 241, 234, 23, 139, 18, 41, 25, 119, 182, 254, 45
],
"rct_signatures": {
"type": 0
}
}