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: e39776752b1c4894608170be049af38d47199152d060d55c770032f4b515e75e
Tx prefix hash: a36dc3928f5b18722401d60d2d7ddd61a40134972555325d90582b04e811526d
Tx public key: 132a155aeeb30b0c3a858deab6dc998bf0475f44869e45ea2044d5e3f9abbfa9
| Timestamp: 1779948764 | Timestamp [UTC]: 2026-05-28 06:12:44 | Age [y:d:h:m:s]: 00:011:18:34:03 |
| Block: 3592 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4294 | RingCT/type: yes/0 |
| Extra: 01132a155aeeb30b0c3a858deab6dc998bf0475f44869e45ea2044d5e3f9abbfa902090000000126697be300 | ||
1 output(s) for total of 34.944207347036 HMNY
| stealth address | amount | amount idx | tag |
| 00: d511066bda1da572a2b99324376dc075e13f47e5d9a8c54859fc8ba163d33183 | 34.944207347036 | 4337 of 0 | <e1> |
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": 3652,
"vin": [ {
"gen": {
"height": 3592
}
}
],
"vout": [ {
"amount": 34944207347036,
"target": {
"tagged_key": {
"key": "d511066bda1da572a2b99324376dc075e13f47e5d9a8c54859fc8ba163d33183",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 19, 42, 21, 90, 238, 179, 11, 12, 58, 133, 141, 234, 182, 220, 153, 139, 240, 71, 95, 68, 134, 158, 69, 234, 32, 68, 213, 227, 249, 171, 191, 169, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}