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: f223cf05f48e5a0fd802df0e07136ffd72ccab953f680cd67163b532ab843397
Tx prefix hash: e48410440675a5dc39c173d82dffded8e761c771fbf6e47e63e841cb1da92afa
Tx public key: e4aac849bdf9f61e4ebad0133f42fdb127bc215a6cad33897ac7a817bfdcbca1
| Timestamp: 1779766887 | Timestamp [UTC]: 2026-05-26 03:41:27 | Age [y:d:h:m:s]: 00:013:23:57:23 |
| Block: 1976 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5971 | RingCT/type: yes/0 |
| Extra: 01e4aac849bdf9f61e4ebad0133f42fdb127bc215a6cad33897ac7a817bfdcbca102090000000226697be300 | ||
1 output(s) for total of 35.052081283449 HMNY
| stealth address | amount | amount idx | tag |
| 00: a829650b98e4ec830e85a58980ea6ba9bbc1f39f6649f4c547422210b4d41a71 | 35.052081283449 | 2248 of 0 | <e7> |
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": 2036,
"vin": [ {
"gen": {
"height": 1976
}
}
],
"vout": [ {
"amount": 35052081283449,
"target": {
"tagged_key": {
"key": "a829650b98e4ec830e85a58980ea6ba9bbc1f39f6649f4c547422210b4d41a71",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 228, 170, 200, 73, 189, 249, 246, 30, 78, 186, 208, 19, 63, 66, 253, 177, 39, 188, 33, 90, 108, 173, 51, 137, 122, 199, 168, 23, 191, 220, 188, 161, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}