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: c5bc65d9c8a02ac7a437a6875b658c901e3b47b5add8ebd3b769605445d54ae6
Tx prefix hash: 10eb9d63f35f6f4ca02f0e13e668e7d7173bb7e3dca618e929700d2918bd8f6e
Tx public key: 0fc3faa9e5aefe462f782dfe78774954dd336bb647082e8e7b143082bc0fe1e2
| Timestamp: 1780014711 | Timestamp [UTC]: 2026-05-29 00:31:51 | Age [y:d:h:m:s]: 00:011:01:04:06 |
| Block: 4113 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3773 | RingCT/type: yes/0 |
| Extra: 010fc3faa9e5aefe462f782dfe78774954dd336bb647082e8e7b143082bc0fe1e202090000000226697be300 | ||
1 output(s) for total of 34.912122702320 HMNY
| stealth address | amount | amount idx | tag |
| 00: d79d4e12228381afd8eb6d09f36aeae3b5c4cc2dd9801aa5157660aad0af47e2 | 34.912122702320 | 5126 of 0 | <4a> |
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": 4173,
"vin": [ {
"gen": {
"height": 4113
}
}
],
"vout": [ {
"amount": 34912122702320,
"target": {
"tagged_key": {
"key": "d79d4e12228381afd8eb6d09f36aeae3b5c4cc2dd9801aa5157660aad0af47e2",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 15, 195, 250, 169, 229, 174, 254, 70, 47, 120, 45, 254, 120, 119, 73, 84, 221, 51, 107, 182, 71, 8, 46, 142, 123, 20, 48, 130, 188, 15, 225, 226, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}