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: 5333ba29b30faae3397b7a166b4661ba232fe332cb29be2d054566460f435003
Tx prefix hash: 75613b98da845685f4c347c8b0da51646291848c3c14cbefe58e21e57eb5d44e
Tx public key: e559b76ebc13f920bb22a9de0572eb08e29fbb6e17e0eee0ae1abf62a3f2bda0
| Timestamp: 1780392425 | Timestamp [UTC]: 2026-06-02 09:27:05 | Age [y:d:h:m:s]: 00:006:15:19:42 |
| Block: 5219 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2667 | RingCT/type: yes/0 |
| Extra: 01e559b76ebc13f920bb22a9de0572eb08e29fbb6e17e0eee0ae1abf62a3f2bda002090000000126697be300 | ||
1 output(s) for total of 34.835934500864 HMNY
| stealth address | amount | amount idx | tag |
| 00: e4910d64e26234e5365c4d840e2a39c53f9f7d0899536af8ffe8f0706e98370d | 34.835934500864 | 6604 of 0 | <19> |
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": 5279,
"vin": [ {
"gen": {
"height": 5219
}
}
],
"vout": [ {
"amount": 34835934500864,
"target": {
"tagged_key": {
"key": "e4910d64e26234e5365c4d840e2a39c53f9f7d0899536af8ffe8f0706e98370d",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 229, 89, 183, 110, 188, 19, 249, 32, 187, 34, 169, 222, 5, 114, 235, 8, 226, 159, 187, 110, 23, 224, 238, 224, 174, 26, 191, 98, 163, 242, 189, 160, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}