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: bc80bd9150aeda27bce89457d0ca0b5c658ca4235fdc0136224b54d43e57c302
Tx prefix hash: 6f3769465c919ad14ea96a0d9b9b7d931603c66e035aac9b6164cbaab2425829
Tx public key: 7931a5ea90a3ae111b28e869153df14cb80df48010a8ac0422dd768595ffe912
| Timestamp: 1779872105 | Timestamp [UTC]: 2026-05-27 08:55:05 | Age [y:d:h:m:s]: 00:012:16:40:52 |
| Block: 2828 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5058 | RingCT/type: yes/0 |
| Extra: 017931a5ea90a3ae111b28e869153df14cb80df48010a8ac0422dd768595ffe91202090000000126697be300 | ||
1 output(s) for total of 34.995165715836 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f0661b0265e0ada79b3332efddc1bc4f2cf7704a1da1861813d664635580cfa | 34.995165715836 | 3346 of 0 | <72> |
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": 2888,
"vin": [ {
"gen": {
"height": 2828
}
}
],
"vout": [ {
"amount": 34995165715836,
"target": {
"tagged_key": {
"key": "8f0661b0265e0ada79b3332efddc1bc4f2cf7704a1da1861813d664635580cfa",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 121, 49, 165, 234, 144, 163, 174, 17, 27, 40, 232, 105, 21, 61, 241, 76, 184, 13, 244, 128, 16, 168, 172, 4, 34, 221, 118, 133, 149, 255, 233, 18, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}