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: b3723454e716e7194b90c04edc76aac64069477e9c794a994d48ad7b3cc07ad7
Tx prefix hash: eb13a19217db0da5fe046cedad84b385007095a114bbab5cb038c344d956d9db
Tx public key: 4d365ccc323ed3f431f3937658548498aa0e79a85f4a8198eb3d4e096431742e
| Timestamp: 1780773577 | Timestamp [UTC]: 2026-06-06 19:19:37 | Age [y:d:h:m:s]: 00:002:08:31:21 |
| Block: 6691 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1275 | RingCT/type: yes/0 |
| Extra: 014d365ccc323ed3f431f3937658548498aa0e79a85f4a8198eb3d4e096431742e020900000001e49593ff00 | ||
1 output(s) for total of 34.748096011856 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5ca85a074af2a98031e8531e340318c612f8e26e1898bf477f026e8e51007bf | 34.748096011856 | 8251 of 0 | <fd> |
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": 6751,
"vin": [ {
"gen": {
"height": 6691
}
}
],
"vout": [ {
"amount": 34748096011856,
"target": {
"tagged_key": {
"key": "c5ca85a074af2a98031e8531e340318c612f8e26e1898bf477f026e8e51007bf",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 77, 54, 92, 204, 50, 62, 211, 244, 49, 243, 147, 118, 88, 84, 132, 152, 170, 14, 121, 168, 95, 74, 129, 152, 235, 61, 78, 9, 100, 49, 116, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}