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: 2db478e639d70db32ea3916d0bd24e6d976b0a82af0afdf4c96be65cd52a3864
Tx prefix hash: e8b3cc758de65a747f13d46a5b669ba4532045b70af6f7407b4d683ffb37695b
Tx public key: d13d394c6ebf50cef83faa5d72834295fa8f7b5be4a61f49bce77a4f5111bbad
| Timestamp: 1779971497 | Timestamp [UTC]: 2026-05-28 12:31:37 | Age [y:d:h:m:s]: 00:011:12:15:10 |
| Block: 3850 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4036 | RingCT/type: yes/0 |
| Extra: 01d13d394c6ebf50cef83faa5d72834295fa8f7b5be4a61f49bce77a4f5111bbad02090000000326697be300 | ||
1 output(s) for total of 34.927015658152 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5bbeeaf0d54052203224714597e36372625e8db4c8338b6a7f3ce0fed0eeecbd | 34.927015658152 | 4702 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": 3910,
"vin": [ {
"gen": {
"height": 3850
}
}
],
"vout": [ {
"amount": 34927015658152,
"target": {
"tagged_key": {
"key": "5bbeeaf0d54052203224714597e36372625e8db4c8338b6a7f3ce0fed0eeecbd",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 209, 61, 57, 76, 110, 191, 80, 206, 248, 63, 170, 93, 114, 131, 66, 149, 250, 143, 123, 91, 228, 166, 31, 73, 188, 231, 122, 79, 81, 17, 187, 173, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}