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: 59f120e6d1b71c9d75a358eec72e0cff6aef99691cb48e98147023265857e7bb
Tx prefix hash: e1137a9401e91076d8653a9347d84fb0ab0f3359d5a67b34937d6f4c29822fb2
Tx public key: 831162f34ff3f3e3b4d6375a8a75210548219e0d523df5d8ca8bbe1f9eee6563
| Timestamp: 1779799432 | Timestamp [UTC]: 2026-05-26 12:43:52 | Age [y:d:h:m:s]: 00:013:12:52:05 |
| Block: 2293 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5593 | RingCT/type: yes/0 |
| Extra: 01831162f34ff3f3e3b4d6375a8a75210548219e0d523df5d8ca8bbe1f9eee656302090000000326697be300 | ||
1 output(s) for total of 35.030894146111 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84028d2590c109d74e16dc0cb6aa817bf3954f953a5772e85a41683342696ad5 | 35.030894146111 | 2673 of 0 | <a7> |
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": 2353,
"vin": [ {
"gen": {
"height": 2293
}
}
],
"vout": [ {
"amount": 35030894146111,
"target": {
"tagged_key": {
"key": "84028d2590c109d74e16dc0cb6aa817bf3954f953a5772e85a41683342696ad5",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 131, 17, 98, 243, 79, 243, 243, 227, 180, 214, 55, 90, 138, 117, 33, 5, 72, 33, 158, 13, 82, 61, 245, 216, 202, 139, 190, 31, 158, 238, 101, 99, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}