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: 6d630d977002cd8b1ba5452341174e8d17eeede4796de412001d96c8be333847
Tx prefix hash: bb917dd40167eabe7239355f05af3a588cc3fe4c4ca6aac121f55d106cd74ac3
Tx public key: cb0d6a3fb45b341d88ca739557731a57f002b69174e3e08240a0790d7d333b1e
| Timestamp: 1780852709 | Timestamp [UTC]: 2026-06-07 17:18:29 | Age [y:d:h:m:s]: 00:001:08:17:28 |
| Block: 7549 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 337 | RingCT/type: yes/0 |
| Extra: 01cb0d6a3fb45b341d88ca739557731a57f002b69174e3e08240a0790d7d333b1e020900000002e49593ff00 | ||
1 output(s) for total of 34.681462699715 HMNY
| stealth address | amount | amount idx | tag |
| 00: 44aa208e354ea95f4bc8ab43ec01b9984fd3b5993daa073425dabd1b66e5b5e0 | 34.681462699715 | 9317 of 0 | <48> |
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": 7609,
"vin": [ {
"gen": {
"height": 7549
}
}
],
"vout": [ {
"amount": 34681462699715,
"target": {
"tagged_key": {
"key": "44aa208e354ea95f4bc8ab43ec01b9984fd3b5993daa073425dabd1b66e5b5e0",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 203, 13, 106, 63, 180, 91, 52, 29, 136, 202, 115, 149, 87, 115, 26, 87, 240, 2, 182, 145, 116, 227, 224, 130, 64, 160, 121, 13, 125, 51, 59, 30, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}