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: cb529f35d542b13a56533760eea405eebe2a32fd1852308d74d4841f1005e51c
Tx prefix hash: 270f6b926e1ba15346a4286869578860e1183e7a3bb567f07e4d00fbc872602b
Tx public key: cd32a1ece7508b2f3cccd8875b17c0ce4c3dc53d1fb3f05e4d38b81f3ae90321
| Timestamp: 1779897344 | Timestamp [UTC]: 2026-05-27 15:55:44 | Age [y:d:h:m:s]: 00:012:05:16:23 |
| Block: 3113 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4773 | RingCT/type: yes/0 |
| Extra: 01cd32a1ece7508b2f3cccd8875b17c0ce4c3dc53d1fb3f05e4d38b81f3ae9032102090000000126697be300 | ||
1 output(s) for total of 34.976147692490 HMNY
| stealth address | amount | amount idx | tag |
| 00: 45a7f041af394df78284fea6b7d72ef3edc8b2ff8e9b298023711a73a5096982 | 34.976147692490 | 3715 of 0 | <1d> |
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": 3173,
"vin": [ {
"gen": {
"height": 3113
}
}
],
"vout": [ {
"amount": 34976147692490,
"target": {
"tagged_key": {
"key": "45a7f041af394df78284fea6b7d72ef3edc8b2ff8e9b298023711a73a5096982",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 205, 50, 161, 236, 231, 80, 139, 47, 60, 204, 216, 135, 91, 23, 192, 206, 76, 61, 197, 61, 31, 179, 240, 94, 77, 56, 184, 31, 58, 233, 3, 33, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}