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: 304e6e67b375ef560bf51bb25ce2b76318c79507e294f46d107ac72697cd5bc4
Tx prefix hash: 0a1cfc2547266fbaddb955ab3e7aefeb0fc21defffffe39ef416d90599fbb780
Tx public key: b5515d1fc42dff91be6e5c5329a1e2eabe45211f892b9239ce7f336d6e7b9d80
| Timestamp: 1779724247 | Timestamp [UTC]: 2026-05-25 15:50:47 | Age [y:d:h:m:s]: 00:014:08:56:00 |
| Block: 1818 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6068 | RingCT/type: yes/0 |
| Extra: 01b5515d1fc42dff91be6e5c5329a1e2eabe45211f892b9239ce7f336d6e7b9d80020900000003ba6d17be00 | ||
1 output(s) for total of 35.062646218586 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3ea09587ac5bf20066ab997ec953cc7af1ee37c121980b8e02855eb7ac5146e | 35.062646218586 | 2012 of 0 | <ba> |
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": 1878,
"vin": [ {
"gen": {
"height": 1818
}
}
],
"vout": [ {
"amount": 35062646218586,
"target": {
"tagged_key": {
"key": "c3ea09587ac5bf20066ab997ec953cc7af1ee37c121980b8e02855eb7ac5146e",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 181, 81, 93, 31, 196, 45, 255, 145, 190, 110, 92, 83, 41, 161, 226, 234, 190, 69, 33, 31, 137, 43, 146, 57, 206, 127, 51, 109, 110, 123, 157, 128, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}