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: 3a464f1d6ddf5112a2d9f29f637e31293d92358c8742d0d2a9d87ae94dc23bd8
Tx prefix hash: e9b708fe9867be9fc69cf6a42261b9fb6e21b3b3243ef60e4420f2ef4497468d
Tx public key: 8c3a17a2ab28022da34a67802667ba35dc8a48f07a397a00560203853c7974ff
| Timestamp: 1779438098 | Timestamp [UTC]: 2026-05-22 08:21:38 | Age [y:d:h:m:s]: 00:017:17:14:19 |
| Block: 182 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7704 | RingCT/type: yes/0 |
| Extra: 018c3a17a2ab28022da34a67802667ba35dc8a48f07a397a00560203853c7974ff0209000000025cddc08000 | ||
1 output(s) for total of 35.172227469444 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6dd110f297e25a8ff03ce73ce1b65b9d8a780c1b403d1698eeff4de60a3e4003 | 35.172227469444 | 178 of 0 | <33> |
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": 242,
"vin": [ {
"gen": {
"height": 182
}
}
],
"vout": [ {
"amount": 35172227469444,
"target": {
"tagged_key": {
"key": "6dd110f297e25a8ff03ce73ce1b65b9d8a780c1b403d1698eeff4de60a3e4003",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 140, 58, 23, 162, 171, 40, 2, 45, 163, 74, 103, 128, 38, 103, 186, 53, 220, 138, 72, 240, 122, 57, 122, 0, 86, 2, 3, 133, 60, 121, 116, 255, 2, 9, 0, 0, 0, 2, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}