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: 2311c47aa886f56865174c51475f1b6cbfd16e1607aedaaa19929f6273734589
Tx prefix hash: 82603f09eac747f8ef05c3f36f7192eaf0f371a5dd202e7215636109f7bc9709
Tx public key: 65bf3344c4e4f106cf8e54086bc8257541813b41e02c940e722f6b1818df5e0c
| Timestamp: 1779940973 | Timestamp [UTC]: 2026-05-28 04:02:53 | Age [y:d:h:m:s]: 00:011:21:33:04 |
| Block: 3495 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4391 | RingCT/type: yes/0 |
| Extra: 0165bf3344c4e4f106cf8e54086bc8257541813b41e02c940e722f6b1818df5e0c02090000000126697be300 | ||
1 output(s) for total of 34.950673077558 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3485c84cdb27d76e3343096d8be1d17ab085ba0147fc51eda3f4a5670f5403b7 | 34.950673077558 | 4214 of 0 | <f2> |
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": 3555,
"vin": [ {
"gen": {
"height": 3495
}
}
],
"vout": [ {
"amount": 34950673077558,
"target": {
"tagged_key": {
"key": "3485c84cdb27d76e3343096d8be1d17ab085ba0147fc51eda3f4a5670f5403b7",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 101, 191, 51, 68, 196, 228, 241, 6, 207, 142, 84, 8, 107, 200, 37, 117, 65, 129, 59, 65, 224, 44, 148, 14, 114, 47, 107, 24, 24, 223, 94, 12, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}