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: ba0d93cde1bf4aa7bce64543befea691b356931a4321b043eaacf1254095192a
Tx prefix hash: 2f3dcbd58ac756699144b1aab438c0eff7b83053ab239a3ebf1e58085e2d2ddb
Tx public key: b390088bb21a2ce6370e3bed3a39051dab5b98b2763f777f3805a2cf8509cd2b
| Timestamp: 1780900904 | Timestamp [UTC]: 2026-06-08 06:41:44 | Age [y:d:h:m:s]: 00:000:14:30:23 |
| Block: 7813 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 73 | RingCT/type: yes/0 |
| Extra: 01b390088bb21a2ce6370e3bed3a39051dab5b98b2763f777f3805a2cf8509cd2b0209000000014a728a4c00 | ||
1 output(s) for total of 34.664003574036 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4cd1517f6eb98e7b381d98f11afa7f2aec4598aa12a46545f958eda783016ec1 | 34.664003574036 | 9685 of 0 | <29> |
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": 7873,
"vin": [ {
"gen": {
"height": 7813
}
}
],
"vout": [ {
"amount": 34664003574036,
"target": {
"tagged_key": {
"key": "4cd1517f6eb98e7b381d98f11afa7f2aec4598aa12a46545f958eda783016ec1",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 179, 144, 8, 139, 178, 26, 44, 230, 55, 14, 59, 237, 58, 57, 5, 29, 171, 91, 152, 178, 118, 63, 119, 127, 56, 5, 162, 207, 133, 9, 205, 43, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}