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: 5ff01f4a3485bf98d0e086dee8e43b8d0bd0c85ef950db6e7fbf9ccb9813ce2c
Tx prefix hash: 65ee4e57dd897c2990c3beb20c1eb1ee0a2471e41eec41dd15e57681272d6f3f
Tx public key: 7737fc3d53dab432d00832dccd9170ed15a4d1a26bca002ebe6e401e9f618f7b
| Timestamp: 1779874794 | Timestamp [UTC]: 2026-05-27 09:39:54 | Age [y:d:h:m:s]: 00:013:07:29:09 |
| Block: 2868 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5866 | RingCT/type: yes/0 |
| Extra: 017737fc3d53dab432d00832dccd9170ed15a4d1a26bca002ebe6e401e9f618f7b02090000000126697be300 | ||
1 output(s) for total of 34.992495895878 HMNY
| stealth address | amount | amount idx | tag |
| 00: 914073df38245b70077ffad9c0f00996bd0d421e4dd6dd7e6d1a5d871acfb1c2 | 34.992495895878 | 3396 of 0 | <b5> |
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": 2928,
"vin": [ {
"gen": {
"height": 2868
}
}
],
"vout": [ {
"amount": 34992495895878,
"target": {
"tagged_key": {
"key": "914073df38245b70077ffad9c0f00996bd0d421e4dd6dd7e6d1a5d871acfb1c2",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 119, 55, 252, 61, 83, 218, 180, 50, 208, 8, 50, 220, 205, 145, 112, 237, 21, 164, 209, 162, 107, 202, 0, 46, 190, 110, 64, 30, 159, 97, 143, 123, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}