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: 45691a441235cff628a9287c98fe5a580011270c0a0ced0fb817e18ddf239332
Tx prefix hash: 37993e279ae13196ac70b4dd5a2d43c1c1943501ec9b561b6ba9c5b4f83e9d22
Tx public key: ee815c7edc0ec3b3900b7a74f53a357661451b6734986b8959d973b9d8ccd16e
| Timestamp: 1779448416 | Timestamp [UTC]: 2026-05-22 11:13:36 | Age [y:d:h:m:s]: 00:017:16:25:14 |
| Block: 301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7646 | RingCT/type: yes/0 |
| Extra: 01ee815c7edc0ec3b3900b7a74f53a357661451b6734986b8959d973b9d8ccd16e0209000000034438f87f00 | ||
1 output(s) for total of 35.164245169458 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3851db84d142d2987d84cf18409f0daecf7a238054894cbe6348ebc85dd0525e | 35.164245169458 | 297 of 0 | <ac> |
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": 361,
"vin": [ {
"gen": {
"height": 301
}
}
],
"vout": [ {
"amount": 35164245169458,
"target": {
"tagged_key": {
"key": "3851db84d142d2987d84cf18409f0daecf7a238054894cbe6348ebc85dd0525e",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 238, 129, 92, 126, 220, 14, 195, 179, 144, 11, 122, 116, 245, 58, 53, 118, 97, 69, 27, 103, 52, 152, 107, 137, 89, 217, 115, 185, 216, 204, 209, 110, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}