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: 03d503581422f6656b8e22b990ec753e0313920fd369b63c196cf01ac06b0d94
Tx prefix hash: e600837df9643c9df5a86ab7727ed67c4519ddd305fb3b17053c898bc718a626
Tx public key: 4bff9cee1e13ab33c40722babb1161be4a4e2cca4664d9763ec8d05139054605
| Timestamp: 1779986798 | Timestamp [UTC]: 2026-05-28 16:46:38 | Age [y:d:h:m:s]: 00:011:08:49:19 |
| Block: 3962 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3924 | RingCT/type: yes/0 |
| Extra: 014bff9cee1e13ab33c40722babb1161be4a4e2cca4664d9763ec8d0513905460502090000000126697be300 | ||
1 output(s) for total of 34.919555232422 HMNY
| stealth address | amount | amount idx | tag |
| 00: aaeb48d8897c94d2ffb067f40172b4e4bf70c639acd5f2db98b1c7e36b6aa074 | 34.919555232422 | 4884 of 0 | <3a> |
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": 4022,
"vin": [ {
"gen": {
"height": 3962
}
}
],
"vout": [ {
"amount": 34919555232422,
"target": {
"tagged_key": {
"key": "aaeb48d8897c94d2ffb067f40172b4e4bf70c639acd5f2db98b1c7e36b6aa074",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 75, 255, 156, 238, 30, 19, 171, 51, 196, 7, 34, 186, 187, 17, 97, 190, 74, 78, 44, 202, 70, 100, 217, 118, 62, 200, 208, 81, 57, 5, 70, 5, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}