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: 8ae95c3c7889adccf22d9e7e420aa2517bdf9626d045bca9497724f9be6528cb
Tx prefix hash: 1f9593d324c28a7939cfe9575a3f3d93e0991fc30a74e2be6544bc521e33dbc9
Tx public key: d3c2c40b9f6d9cf3147708e612a12b10d955a61ab09a3bed97c7a925bba1fc7f
| Timestamp: 1779649296 | Timestamp [UTC]: 2026-05-24 19:01:36 | Age [y:d:h:m:s]: 00:015:22:07:27 |
| Block: 1477 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7257 | RingCT/type: yes/0 |
| Extra: 01d3c2c40b9f6d9cf3147708e612a12b10d955a61ab09a3bed97c7a925bba1fc7f02090000000aba6d17be00 | ||
1 output(s) for total of 35.085458609596 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d88fec39e4402ebf19fd2122033d899e2ab9299edf02de1f61374a7d5188395 | 35.085458609596 | 1633 of 0 | <13> |
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": 1537,
"vin": [ {
"gen": {
"height": 1477
}
}
],
"vout": [ {
"amount": 35085458609596,
"target": {
"tagged_key": {
"key": "2d88fec39e4402ebf19fd2122033d899e2ab9299edf02de1f61374a7d5188395",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 211, 194, 196, 11, 159, 109, 156, 243, 20, 119, 8, 230, 18, 161, 43, 16, 217, 85, 166, 26, 176, 154, 59, 237, 151, 199, 169, 37, 187, 161, 252, 127, 2, 9, 0, 0, 0, 10, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}