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: bb212775437a2f15d5b67640fe4f8a73b4ab7efd0b44bc7f6827eacbeef3cb69
Tx prefix hash: 60e025c69db9de6f12a3bb7b016552f14769760eb3fec5fa624493b1fe5bb8e8
Tx public key: 82987009e94c4d2416cb82b95d70fecf787699c1f3477d7dbef8ed0d449b4558
| Timestamp: 1779712164 | Timestamp [UTC]: 2026-05-25 12:29:24 | Age [y:d:h:m:s]: 00:014:13:06:33 |
| Block: 1585 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6301 | RingCT/type: yes/0 |
| Extra: 0182987009e94c4d2416cb82b95d70fecf787699c1f3477d7dbef8ed0d449b4558020900000001ba6d17be00 | ||
1 output(s) for total of 35.078231965288 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1bc3907b526ab67ebb20ce820ba8f3aa47db04a656008179575030f30bdf30fb | 35.078231965288 | 1743 of 0 | <7c> |
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": 1645,
"vin": [ {
"gen": {
"height": 1585
}
}
],
"vout": [ {
"amount": 35078231965288,
"target": {
"tagged_key": {
"key": "1bc3907b526ab67ebb20ce820ba8f3aa47db04a656008179575030f30bdf30fb",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 130, 152, 112, 9, 233, 76, 77, 36, 22, 203, 130, 185, 93, 112, 254, 207, 120, 118, 153, 193, 243, 71, 125, 125, 190, 248, 237, 13, 68, 155, 69, 88, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}