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: 80285752f9b07bf4ed5cec923f6a59dc1291da8477e1a3374437bc5c8acf0796
Tx prefix hash: cf96e7a17a5662e318a4ba9e9d3899b7dc528e846cd7d2ff7cf19fb00effd5e9
Tx public key: c841935441ee584117dc4f77d237eb4cc762a7a3db663e2a7e2e26955701ddc0
| Timestamp: 1780137241 | Timestamp [UTC]: 2026-05-30 10:34:01 | Age [y:d:h:m:s]: 00:009:14:12:46 |
| Block: 4971 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2915 | RingCT/type: yes/0 |
| Extra: 01c841935441ee584117dc4f77d237eb4cc762a7a3db663e2a7e2e26955701ddc002090000000126697be300 | ||
1 output(s) for total of 34.852416593942 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9aee0c5938b520b4228defb8c63a6d0ef380a6eae5315044e04073654c30d734 | 34.852416593942 | 6324 of 0 | <b9> |
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": 5031,
"vin": [ {
"gen": {
"height": 4971
}
}
],
"vout": [ {
"amount": 34852416593942,
"target": {
"tagged_key": {
"key": "9aee0c5938b520b4228defb8c63a6d0ef380a6eae5315044e04073654c30d734",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 200, 65, 147, 84, 65, 238, 88, 65, 23, 220, 79, 119, 210, 55, 235, 76, 199, 98, 167, 163, 219, 102, 62, 42, 126, 46, 38, 149, 87, 1, 221, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}