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: 62c39e47a86e5f69abf6c41d69a17c6b9937826b25c9663d03e7f62ce9d60068
Tx prefix hash: 325c3ca211f68c758ab27b549d7ee321d062c5e12029f58d53b01302afcf520e
Tx public key: a06a030b39220a836713fb5ee7fe1bc55185729509c7c1b57ee83a822c4c80a5
| Timestamp: 1780977013 | Timestamp [UTC]: 2026-06-09 03:50:13 | Age [y:d:h:m:s]: 00:000:04:04:01 |
| Block: 7949 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 304 | RingCT/type: yes/0 |
| Extra: 01a06a030b39220a836713fb5ee7fe1bc55185729509c7c1b57ee83a822c4c80a5020900000001e49593ff00 | ||
1 output(s) for total of 34.665060509382 HMNY
| stealth address | amount | amount idx | tag |
| 00: b474af178549c6c49139e9f71199398b555db58dddc47f66f9ddeb893e8eb8df | 34.665060509382 | 9857 of 0 | <e3> |
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": 8009,
"vin": [ {
"gen": {
"height": 7949
}
}
],
"vout": [ {
"amount": 34665060509382,
"target": {
"tagged_key": {
"key": "b474af178549c6c49139e9f71199398b555db58dddc47f66f9ddeb893e8eb8df",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 160, 106, 3, 11, 57, 34, 10, 131, 103, 19, 251, 94, 231, 254, 27, 197, 81, 133, 114, 149, 9, 199, 193, 181, 126, 232, 58, 130, 44, 76, 128, 165, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}