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: f6c561fee94afa5b83a41f7a6aba8b10fec9b14575ea7b717ac5dc763fcd237c
Tx prefix hash: 75105b78d99e815f968f1301a94f027c17a27e1b829b1f9bbc030e8004bb7314
Tx public key: 771a292a62fdcb20a1bf0b3af9d5d813693d00381066c8fb4380779403140f04
| Timestamp: 1779718510 | Timestamp [UTC]: 2026-05-25 14:15:10 | Age [y:d:h:m:s]: 00:014:11:20:47 |
| Block: 1704 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6182 | RingCT/type: yes/0 |
| Extra: 01771a292a62fdcb20a1bf0b3af9d5d813693d00381066c8fb4380779403140f04020900000001ba6d17be00 | ||
1 output(s) for total of 35.070270997483 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6afa5d3fae86bad925d6f04aa0003901bd7e224f8fab16e1d520b16a54891813 | 35.070270997483 | 1875 of 0 | <69> |
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": 1764,
"vin": [ {
"gen": {
"height": 1704
}
}
],
"vout": [ {
"amount": 35070270997483,
"target": {
"tagged_key": {
"key": "6afa5d3fae86bad925d6f04aa0003901bd7e224f8fab16e1d520b16a54891813",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 119, 26, 41, 42, 98, 253, 203, 32, 161, 191, 11, 58, 249, 213, 216, 19, 105, 61, 0, 56, 16, 102, 200, 251, 67, 128, 119, 148, 3, 20, 15, 4, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}