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: 057c26c552525b2042fd9364bc33d32e60dc36f43177e996452c13f13d554da8
Tx prefix hash: fc4c983c1d33035b100f2c4d63f730bef85dcddc1262468c990312a5e2d6ebaa
Tx public key: df97ca27346b09fbbc3c14b6351166ad7c66f9cc7278e81a6d813e0c202d795e
| Timestamp: 1779724776 | Timestamp [UTC]: 2026-05-25 15:59:36 | Age [y:d:h:m:s]: 00:014:08:47:11 |
| Block: 1835 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6051 | RingCT/type: yes/0 |
| Extra: 01df97ca27346b09fbbc3c14b6351166ad7c66f9cc7278e81a6d813e0c202d795e020900000003ba6d17be00 | ||
1 output(s) for total of 35.066508532198 HMNY
| stealth address | amount | amount idx | tag |
| 00: b06e23ede7250c882084ebea9b024f91e7a421a83f704449b7f647fe3603da79 | 35.066508532198 | 2029 of 0 | <6d> |
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": 1895,
"vin": [ {
"gen": {
"height": 1835
}
}
],
"vout": [ {
"amount": 35066508532198,
"target": {
"tagged_key": {
"key": "b06e23ede7250c882084ebea9b024f91e7a421a83f704449b7f647fe3603da79",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 223, 151, 202, 39, 52, 107, 9, 251, 188, 60, 20, 182, 53, 17, 102, 173, 124, 102, 249, 204, 114, 120, 232, 26, 109, 129, 62, 12, 32, 45, 121, 94, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}