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: e6e046dba3443e3cbf8cb5e72f4c0af1b0a7a0dd785d64f20731fb714d9677f6
Tx prefix hash: 832b93f6fcf7176dd3f5e7d73ba41ab246fc4a09bc5ac14939abf8e1d095fccb
Tx public key: f0b87cc65833a1ef3aaef1418e7df7a273f0e2d5ea060209e8a291a20df96be0
| Timestamp: 1780014847 | Timestamp [UTC]: 2026-05-29 00:34:07 | Age [y:d:h:m:s]: 00:011:00:12:40 |
| Block: 4115 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3771 | RingCT/type: yes/0 |
| Extra: 01f0b87cc65833a1ef3aaef1418e7df7a273f0e2d5ea060209e8a291a20df96be002090000000126697be300 | ||
1 output(s) for total of 34.909366333274 HMNY
| stealth address | amount | amount idx | tag |
| 00: 279ee6060be94aed91e4f32e5cc00901e177ca75842c4058c5107f6a77fbd0be | 34.909366333274 | 5130 of 0 | <86> |
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": 4175,
"vin": [ {
"gen": {
"height": 4115
}
}
],
"vout": [ {
"amount": 34909366333274,
"target": {
"tagged_key": {
"key": "279ee6060be94aed91e4f32e5cc00901e177ca75842c4058c5107f6a77fbd0be",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 240, 184, 124, 198, 88, 51, 161, 239, 58, 174, 241, 65, 142, 125, 247, 162, 115, 240, 226, 213, 234, 6, 2, 9, 232, 162, 145, 162, 13, 249, 107, 224, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}