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: 057d9f975a8a37a6a0da3a5376c39cecb7527d6c2050ddedc8168784e3bed054
Tx prefix hash: 82222f6f45ff15873596a130ccadb3c63d947e7efe892a8f571a1c85efd26edb
Tx public key: 2c15634799fb4286d0c9171ad4d35f945b78fc76a0de072b376b847fa1911186
| Timestamp: 1779983613 | Timestamp [UTC]: 2026-05-28 15:53:33 | Age [y:d:h:m:s]: 00:011:08:53:14 |
| Block: 3947 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3939 | RingCT/type: yes/0 |
| Extra: 012c15634799fb4286d0c9171ad4d35f945b78fc76a0de072b376b847fa191118602090000000726697be300 | ||
1 output(s) for total of 34.920554304155 HMNY
| stealth address | amount | amount idx | tag |
| 00: 925d48a2c4bc5daede180a43a8f7224876d71fb78bae641de6943d1c1fc26737 | 34.920554304155 | 4856 of 0 | <f3> |
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": 4007,
"vin": [ {
"gen": {
"height": 3947
}
}
],
"vout": [ {
"amount": 34920554304155,
"target": {
"tagged_key": {
"key": "925d48a2c4bc5daede180a43a8f7224876d71fb78bae641de6943d1c1fc26737",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 44, 21, 99, 71, 153, 251, 66, 134, 208, 201, 23, 26, 212, 211, 95, 148, 91, 120, 252, 118, 160, 222, 7, 43, 55, 107, 132, 127, 161, 145, 17, 134, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}