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: ccdb4cd0aad9a195e710066a7a6184b4cc3f62681a5afac5db9b49027f4d9cb7
Tx prefix hash: ea2eca7687a2bbf9b44f174ba66cdeaf33b43b66a3c962accce0bea9efcc176e
Tx public key: d3bc2f5661ef970e55aa76a92fa9cedf95c519ec242c758c1ac16d0f56b1dffd
| Timestamp: 1779464006 | Timestamp [UTC]: 2026-05-22 15:33:26 | Age [y:d:h:m:s]: 00:017:12:59:36 |
| Block: 484 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7545 | RingCT/type: yes/0 |
| Extra: 01d3bc2f5661ef970e55aa76a92fa9cedf95c519ec242c758c1ac16d0f56b1dffd02090000000793369e7d00 | ||
1 output(s) for total of 35.151973402662 HMNY
| stealth address | amount | amount idx | tag |
| 00: cfeea695910cd9bc588ade37d8afe7186978a319374aa63b0b15ed296c7b0278 | 35.151973402662 | 488 of 0 | <b6> |
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": 544,
"vin": [ {
"gen": {
"height": 484
}
}
],
"vout": [ {
"amount": 35151973402662,
"target": {
"tagged_key": {
"key": "cfeea695910cd9bc588ade37d8afe7186978a319374aa63b0b15ed296c7b0278",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 211, 188, 47, 86, 97, 239, 151, 14, 85, 170, 118, 169, 47, 169, 206, 223, 149, 197, 25, 236, 36, 44, 117, 140, 26, 193, 109, 15, 86, 177, 223, 253, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}