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: c65f841c40d03fd589dd67cc3280f98886360478995e3043256e9d1e78c94961
Tx prefix hash: 9d292a7c3f3c7e36c3889a2036f8d7ad029b0b91012d8ab203d3a266f2a1742f
Tx public key: d9170bbd294a8a735b8831581b9825eccdbbdf17c70a6b4a5ed733c67fe4f9b2
| Timestamp: 1780396422 | Timestamp [UTC]: 2026-06-02 10:33:42 | Age [y:d:h:m:s]: 00:006:15:02:15 |
| Block: 5253 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2633 | RingCT/type: yes/0 |
| Extra: 01d9170bbd294a8a735b8831581b9825eccdbbdf17c70a6b4a5ed733c67fe4f9b202090000000126697be300 | ||
1 output(s) for total of 34.833675466710 HMNY
| stealth address | amount | amount idx | tag |
| 00: c398c23472a3039837730a36e2d4632638e9fd7d54b93c2a3acf771bfff2b4a3 | 34.833675466710 | 6652 of 0 | <46> |
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": 5313,
"vin": [ {
"gen": {
"height": 5253
}
}
],
"vout": [ {
"amount": 34833675466710,
"target": {
"tagged_key": {
"key": "c398c23472a3039837730a36e2d4632638e9fd7d54b93c2a3acf771bfff2b4a3",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 217, 23, 11, 189, 41, 74, 138, 115, 91, 136, 49, 88, 27, 152, 37, 236, 205, 187, 223, 23, 199, 10, 107, 74, 94, 215, 51, 198, 127, 228, 249, 178, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}