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: 6e677a94c7a9af30a9380fe169d12502ca86e8da8134e16521cf5cdb1a901dec
Tx prefix hash: 3d1755cf7f40f5828e118f9d0d00e224fcb157902824fff506f6fbcf64900988
Tx public key: 85231a52f0b6b37502963d134a2e3952f4300bf65402ea11bb18ac5f26952835
| Timestamp: 1780807138 | Timestamp [UTC]: 2026-06-07 04:38:58 | Age [y:d:h:m:s]: 00:001:20:56:59 |
| Block: 6961 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 925 | RingCT/type: yes/0 |
| Extra: 0185231a52f0b6b37502963d134a2e3952f4300bf65402ea11bb18ac5f26952835020900000001e49593ff00 | ||
1 output(s) for total of 34.720380544934 HMNY
| stealth address | amount | amount idx | tag |
| 00: c56f316fe03c337fa58c760a00e4f1f61d7ed846b16afe0b3d0fcb55bde2da1d | 34.720380544934 | 8585 of 0 | <70> |
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": 7021,
"vin": [ {
"gen": {
"height": 6961
}
}
],
"vout": [ {
"amount": 34720380544934,
"target": {
"tagged_key": {
"key": "c56f316fe03c337fa58c760a00e4f1f61d7ed846b16afe0b3d0fcb55bde2da1d",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 133, 35, 26, 82, 240, 182, 179, 117, 2, 150, 61, 19, 74, 46, 57, 82, 244, 48, 11, 246, 84, 2, 234, 17, 187, 24, 172, 95, 38, 149, 40, 53, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}