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: 0d1618acd4f4933666559fcf0b875674333c8d0d0690f71f92229055cc3d1b45
Tx prefix hash: 39510adad80d5f62a74328f69092d306ef6f45d22975f21e0a1f82ec84684ae3
Tx public key: e08ac2afe060a6c611b016d444ceba7d22c0bb977b9f56a27eb40c9ee7b4f245
| Timestamp: 1779720479 | Timestamp [UTC]: 2026-05-25 14:47:59 | Age [y:d:h:m:s]: 00:014:12:01:49 |
| Block: 1748 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6172 | RingCT/type: yes/0 |
| Extra: 01e08ac2afe060a6c611b016d444ceba7d22c0bb977b9f56a27eb40c9ee7b4f245020900000007ba6d17be00 | ||
1 output(s) for total of 35.067327903903 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7478170ba95f6e88b19bcab46719db86002083474bbcd649ff123006acf6565d | 35.067327903903 | 1926 of 0 | <64> |
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": 1808,
"vin": [ {
"gen": {
"height": 1748
}
}
],
"vout": [ {
"amount": 35067327903903,
"target": {
"tagged_key": {
"key": "7478170ba95f6e88b19bcab46719db86002083474bbcd649ff123006acf6565d",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 224, 138, 194, 175, 224, 96, 166, 198, 17, 176, 22, 212, 68, 206, 186, 125, 34, 192, 187, 151, 123, 159, 86, 162, 126, 180, 12, 158, 231, 180, 242, 69, 2, 9, 0, 0, 0, 7, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}