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: f6c1e953a74f339bd2160f77a3246eb375c0332d8e38a5dff49beb2d7d357a7e
Tx prefix hash: bbd3e6fc3b647be0623db76ef58ebecd81567eead21d4d858cac90def2f386ce
Tx public key: 94c788e545e80e450fff4ad1976ad06c0e12170345f885d3f1cb306fd4d38d95
| Timestamp: 1779442815 | Timestamp [UTC]: 2026-05-22 09:40:15 | Age [y:d:h:m:s]: 00:017:17:00:21 |
| Block: 227 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7669 | RingCT/type: yes/0 |
| Extra: 0194c788e545e80e450fff4ad1976ad06c0e12170345f885d3f1cb306fd4d38d950209000000034438f87f00 | ||
1 output(s) for total of 35.169208739618 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5fc5765c42d96c142ee938842bb39136a1d41b168cd53111829e1a91e42a281a | 35.169208739618 | 223 of 0 | <b1> |
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": 287,
"vin": [ {
"gen": {
"height": 227
}
}
],
"vout": [ {
"amount": 35169208739618,
"target": {
"tagged_key": {
"key": "5fc5765c42d96c142ee938842bb39136a1d41b168cd53111829e1a91e42a281a",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 148, 199, 136, 229, 69, 232, 14, 69, 15, 255, 74, 209, 151, 106, 208, 108, 14, 18, 23, 3, 69, 248, 133, 211, 241, 203, 48, 111, 212, 211, 141, 149, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}