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: ac4121eb683de0d3d7f7b001715cc0774df88d0e3ef40c8c97d1536e9297c85d
Tx prefix hash: cd0dc748394c9789db625957570bd62fe5b9f5508e1cc319a72d8c1f9c753636
Tx public key: 9c34cbac6b8c41be16dd9badeaeb5cb420a65d18cb1dffc2d04a4c7229e62a75
| Timestamp: 1780742463 | Timestamp [UTC]: 2026-06-06 10:41:03 | Age [y:d:h:m:s]: 00:002:14:54:54 |
| Block: 6424 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1462 | RingCT/type: yes/0 |
| Extra: 019c34cbac6b8c41be16dd9badeaeb5cb420a65d18cb1dffc2d04a4c7229e62a75020900000005e49593ff00 | ||
1 output(s) for total of 34.755961015722 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e01e4943eade57cf2ed00ff2637418c7c7b8575dc8052b118a8a8bae92230e3 | 34.755961015722 | 7915 of 0 | <cb> |
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": 6484,
"vin": [ {
"gen": {
"height": 6424
}
}
],
"vout": [ {
"amount": 34755961015722,
"target": {
"tagged_key": {
"key": "8e01e4943eade57cf2ed00ff2637418c7c7b8575dc8052b118a8a8bae92230e3",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 156, 52, 203, 172, 107, 140, 65, 190, 22, 221, 155, 173, 234, 235, 92, 180, 32, 166, 93, 24, 203, 29, 255, 194, 208, 74, 76, 114, 41, 230, 42, 117, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}