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: ed4e6987f0d33b71e7c514f7f735fe3b92feead2cdf610cf27d1a84dfbb2000d
Tx prefix hash: 9c3592cc1cbaf6cd15d1359d97a9c2dd812045e080224e95e6aa4bf706933228
Tx public key: 45fbb58a87b503e61186dc5b938ca21bd2a88b6f4a4314561eaf234c096f7c80
| Timestamp: 1779645054 | Timestamp [UTC]: 2026-05-24 17:50:54 | Age [y:d:h:m:s]: 00:015:08:58:54 |
| Block: 1439 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6479 | RingCT/type: yes/0 |
| Extra: 0145fbb58a87b503e61186dc5b938ca21bd2a88b6f4a4314561eaf234c096f7c80020900000002ba6d17be00 | ||
1 output(s) for total of 35.088001671837 HMNY
| stealth address | amount | amount idx | tag |
| 00: f2cec41f51e2a404e1ef2df1584d6857777defe74ca4b075f53a3e405bacd52b | 35.088001671837 | 1593 of 0 | <ce> |
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": 1499,
"vin": [ {
"gen": {
"height": 1439
}
}
],
"vout": [ {
"amount": 35088001671837,
"target": {
"tagged_key": {
"key": "f2cec41f51e2a404e1ef2df1584d6857777defe74ca4b075f53a3e405bacd52b",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 69, 251, 181, 138, 135, 181, 3, 230, 17, 134, 220, 91, 147, 140, 162, 27, 210, 168, 139, 111, 74, 67, 20, 86, 30, 175, 35, 76, 9, 111, 124, 128, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}