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: 810910af2c678faa66fe8c2d85fc244a0b3a7e62f04671a2b355aaea7499082b
Tx prefix hash: 0e42842ed825255c689a6d193ecdc219a4076aee163502c539a144b219757325
Tx public key: cd393166d908503d8c6a6418ab28e9b37fcee2f5be1989bfbd03de7e1c8fc6f3
| Timestamp: 1779944326 | Timestamp [UTC]: 2026-05-28 04:58:46 | Age [y:d:h:m:s]: 00:011:23:34:16 |
| Block: 3542 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4486 | RingCT/type: yes/0 |
| Extra: 01cd393166d908503d8c6a6418ab28e9b37fcee2f5be1989bfbd03de7e1c8fc6f302090000000426697be300 | ||
1 output(s) for total of 34.951758048433 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8b001da8e0985a5756074a0fe26c2abe2320bd35874b5ab0116c7e006b830976 | 34.951758048433 | 4270 of 0 | <2b> |
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": 3602,
"vin": [ {
"gen": {
"height": 3542
}
}
],
"vout": [ {
"amount": 34951758048433,
"target": {
"tagged_key": {
"key": "8b001da8e0985a5756074a0fe26c2abe2320bd35874b5ab0116c7e006b830976",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 205, 57, 49, 102, 217, 8, 80, 61, 140, 106, 100, 24, 171, 40, 233, 179, 127, 206, 226, 245, 190, 25, 137, 191, 189, 3, 222, 126, 28, 143, 198, 243, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}