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: 489f33850a0f5cae7c4d9deef1a16eff3db9f62370ebed66ac503d22a9ccdc44
Tx prefix hash: 2dfc2a4436b51cf0f546e2e2847ac88c563dcf05d02ab1e52577b23b82baa325
Tx public key: 58b7170a7c2c6dafa36a21c0f7a85b8d5e80c4ad8a1ec6587f6f025f1b4e29df
| Timestamp: 1779852539 | Timestamp [UTC]: 2026-05-27 03:28:59 | Age [y:d:h:m:s]: 00:021:05:07:15 |
| Block: 2554 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6191 | RingCT/type: yes/0 |
| Extra: 0158b7170a7c2c6dafa36a21c0f7a85b8d5e80c4ad8a1ec6587f6f025f1b4e29df02090000000126697be300 | ||
1 output(s) for total of 35.024848660072 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e057f2e271e819131529dfe23b5c5663ba04f768d2472a6918ee77af22620f7 | 35.024848660072 | 3006 of 0 | <53> |
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": 2614,
"vin": [ {
"gen": {
"height": 2554
}
}
],
"vout": [ {
"amount": 35024848660072,
"target": {
"tagged_key": {
"key": "4e057f2e271e819131529dfe23b5c5663ba04f768d2472a6918ee77af22620f7",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 88, 183, 23, 10, 124, 44, 109, 175, 163, 106, 33, 192, 247, 168, 91, 141, 94, 128, 196, 173, 138, 30, 198, 88, 127, 111, 2, 95, 27, 78, 41, 223, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}