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: 347365b84dad4e961da66ac75da9df43bbad13e3af2ced0606111b155d38a96b
Tx prefix hash: 9edb4446943115a34559d203452f8d438bca18d313678e37d2127de1941240b3
Tx public key: 22f99c4c8c09aa178d4130db82dcafd0f99c67ffbefa4521f3d42c0adb5d981d
| Timestamp: 1779887952 | Timestamp [UTC]: 2026-05-27 13:19:12 | Age [y:d:h:m:s]: 00:012:12:16:45 |
| Block: 3033 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4853 | RingCT/type: yes/0 |
| Extra: 0122f99c4c8c09aa178d4130db82dcafd0f99c67ffbefa4521f3d42c0adb5d981d02090000000326697be300 | ||
1 output(s) for total of 34.981485041376 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1c123e60f0d857e35149dfa8c3d3bd6f22145ae36ee2d78651f337a99d06c08f | 34.981485041376 | 3605 of 0 | <07> |
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": 3093,
"vin": [ {
"gen": {
"height": 3033
}
}
],
"vout": [ {
"amount": 34981485041376,
"target": {
"tagged_key": {
"key": "1c123e60f0d857e35149dfa8c3d3bd6f22145ae36ee2d78651f337a99d06c08f",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 34, 249, 156, 76, 140, 9, 170, 23, 141, 65, 48, 219, 130, 220, 175, 208, 249, 156, 103, 255, 190, 250, 69, 33, 243, 212, 44, 10, 219, 93, 152, 29, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}