For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 3328923400b6cfe5783dbca4cd387ed0ad47343b77be2830bfa02fdd2b5ff007
Tx prefix hash: fccf8fc51c47980a5045827010473e7d24fc1868cbac907745d15e3f20456ebe
Tx public key: 9391605e28036807aed02f1cef0fe811bafda4ced6b5dc9e450d5f63f7cb3d7a
| Timestamp: 1780815318 | Timestamp [UTC]: 2026-06-07 06:55:18 | Age [y:d:h:m:s]: 00:001:16:23:35 |
| Block: 7056 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 830 | RingCT/type: yes/0 |
| Extra: 019391605e28036807aed02f1cef0fe811bafda4ced6b5dc9e450d5f63f7cb3d7a020900000001e49593ff00 | ||
1 output(s) for total of 34.714089841199 HMNY
| stealth address | amount | amount idx | tag |
| 00: 852faa6eb14ff598d3992a1ba8be6f2afb4f06843786166c1c3393d110dc90f6 | 34.714089841199 | 8700 of 0 | <85> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 7116,
"vin": [ {
"gen": {
"height": 7056
}
}
],
"vout": [ {
"amount": 34714089841199,
"target": {
"tagged_key": {
"key": "852faa6eb14ff598d3992a1ba8be6f2afb4f06843786166c1c3393d110dc90f6",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 147, 145, 96, 94, 40, 3, 104, 7, 174, 208, 47, 28, 239, 15, 232, 17, 186, 253, 164, 206, 214, 181, 220, 158, 69, 13, 95, 99, 247, 203, 61, 122, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}