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: 40aed8ab6a31109c80d726eacec1979759aa26b1e98ceb7750e81ff7fbc1e6e8
Tx prefix hash: 38faf3fe87cbc850e2cad6890dd686ee6ddd8d038780821cdd304d7795a96504
Tx public key: 1d5fde1abce3b713f58c23bf30c6309f670ffd1080f1ea6832f8194757dde8c5
| Timestamp: 1779458903 | Timestamp [UTC]: 2026-05-22 14:08:23 | Age [y:d:h:m:s]: 00:017:10:38:24 |
| Block: 415 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7471 | RingCT/type: yes/0 |
| Extra: 011d5fde1abce3b713f58c23bf30c6309f670ffd1080f1ea6832f8194757dde8c502090000000293369e7d00 | ||
1 output(s) for total of 35.156599959231 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70bb108f2a5beb7d650f74580ccaf5806f149b412daa77870457a079021fa51e | 35.156599959231 | 419 of 0 | <a0> |
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": 475,
"vin": [ {
"gen": {
"height": 415
}
}
],
"vout": [ {
"amount": 35156599959231,
"target": {
"tagged_key": {
"key": "70bb108f2a5beb7d650f74580ccaf5806f149b412daa77870457a079021fa51e",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 29, 95, 222, 26, 188, 227, 183, 19, 245, 140, 35, 191, 48, 198, 48, 159, 103, 15, 253, 16, 128, 241, 234, 104, 50, 248, 25, 71, 87, 221, 232, 197, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}