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: 23d7eb3e4cde947395128387ab5fef1266d657be0af6a412d4af2abcff99aac9
Tx prefix hash: 458a48136afe5a4b940aa3cb4e6ffc3b701d58fa6693c72b0e6fdd16c76bcaa3
Tx public key: 38ba72b189d9cfec81f359cb046a506fa662e2feb21e37dc5d7d187a96858780
| Timestamp: 1779467642 | Timestamp [UTC]: 2026-05-22 16:34:02 | Age [y:d:h:m:s]: 00:017:09:01:55 |
| Block: 533 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7353 | RingCT/type: yes/0 |
| Extra: 0138ba72b189d9cfec81f359cb046a506fa662e2feb21e37dc5d7d187a9685878002090000000593369e7d00 | ||
1 output(s) for total of 35.148688246695 HMNY
| stealth address | amount | amount idx | tag |
| 00: fa4a10d0a8e394d5b602ca8ea85b56222b7bddf89bd1f966aedbe9459570eb30 | 35.148688246695 | 537 of 0 | <7e> |
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": 593,
"vin": [ {
"gen": {
"height": 533
}
}
],
"vout": [ {
"amount": 35148688246695,
"target": {
"tagged_key": {
"key": "fa4a10d0a8e394d5b602ca8ea85b56222b7bddf89bd1f966aedbe9459570eb30",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 56, 186, 114, 177, 137, 217, 207, 236, 129, 243, 89, 203, 4, 106, 80, 111, 166, 98, 226, 254, 178, 30, 55, 220, 93, 125, 24, 122, 150, 133, 135, 128, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}