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: 1935ec7ee4bdd90c0bf77dfbb33e082672d0da9615ac31dc9af4e71a6c55baf4
Tx prefix hash: 6c7c8e0a1fb777a2a49ad85112f8ad6b523d04f46677a3684c85ba836352f464
Tx public key: 82f473a076dc6ad38df2887c8616888996bac9df514d15647ba78bc776949045
| Timestamp: 1779777209 | Timestamp [UTC]: 2026-05-26 06:33:29 | Age [y:d:h:m:s]: 00:020:01:46:06 |
| Block: 2074 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6671 | RingCT/type: yes/0 |
| Extra: 0182f473a076dc6ad38df2887c8616888996bac9df514d15647ba78bc77694904502090000000126697be300 | ||
1 output(s) for total of 35.045529948656 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a48c33c5c83628f6ab0a23cda2b046fb2d3448e274781353ee125bfd535ba2c | 35.045529948656 | 2380 of 0 | <92> |
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": 2134,
"vin": [ {
"gen": {
"height": 2074
}
}
],
"vout": [ {
"amount": 35045529948656,
"target": {
"tagged_key": {
"key": "7a48c33c5c83628f6ab0a23cda2b046fb2d3448e274781353ee125bfd535ba2c",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 130, 244, 115, 160, 118, 220, 106, 211, 141, 242, 136, 124, 134, 22, 136, 137, 150, 186, 201, 223, 81, 77, 21, 100, 123, 167, 139, 199, 118, 148, 144, 69, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}