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: 55df5626c0faf32d0ae7b9f663b0eb83dbca2af21b15e3239f02e3064f3d3d95
Tx prefix hash: ed5b62f56c7a67497116d6dc821d3b0acb050eeffa8da86feb2f8f0cdd32ca5e
Tx public key: d3ce61f9b348587c560498228929a49b54c2eabfd875117cb0c3aaa653f29d16
| Timestamp: 1780698103 | Timestamp [UTC]: 2026-06-05 22:21:43 | Age [y:d:h:m:s]: 00:007:12:40:33 |
| Block: 6020 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2725 | RingCT/type: yes/0 |
| Extra: 01d3ce61f9b348587c560498228929a49b54c2eabfd875117cb0c3aaa653f29d16020900000004e49593ff00 | ||
1 output(s) for total of 34.782753223397 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f40a1ae6d1177f9d9a4012fa2dae343600da6452f88ae2604f72942012a4ef7 | 34.782753223397 | 7487 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": 6080,
"vin": [ {
"gen": {
"height": 6020
}
}
],
"vout": [ {
"amount": 34782753223397,
"target": {
"tagged_key": {
"key": "6f40a1ae6d1177f9d9a4012fa2dae343600da6452f88ae2604f72942012a4ef7",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 211, 206, 97, 249, 179, 72, 88, 124, 86, 4, 152, 34, 137, 41, 164, 155, 84, 194, 234, 191, 216, 117, 17, 124, 176, 195, 170, 166, 83, 242, 157, 22, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}