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: aee73fd7c09a9661d08bff746d9c43f576d7ea61c7dc515de875a8b49cde7b89
Tx prefix hash: a03daded72133e662af681220a1b591ed02deb5d4009b52cdee9181e7907f8fe
Tx public key: 569315b9278bb9e65686f0f99d9c4f8aa1e60f76d41fae82b64f8d5c730170b9
| Timestamp: 1780001929 | Timestamp [UTC]: 2026-05-28 20:58:49 | Age [y:d:h:m:s]: 00:011:04:37:08 |
| Block: 4060 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3826 | RingCT/type: yes/0 |
| Extra: 01569315b9278bb9e65686f0f99d9c4f8aa1e60f76d41fae82b64f8d5c730170b902090000000526697be300 | ||
1 output(s) for total of 34.915649467129 HMNY
| stealth address | amount | amount idx | tag |
| 00: 94ed5ed2e3f6fa642862b9bb4b4dd8eb7b1198e8469cef99c3b4fa9d7d0107f9 | 34.915649467129 | 5032 of 0 | <4e> |
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": 4120,
"vin": [ {
"gen": {
"height": 4060
}
}
],
"vout": [ {
"amount": 34915649467129,
"target": {
"tagged_key": {
"key": "94ed5ed2e3f6fa642862b9bb4b4dd8eb7b1198e8469cef99c3b4fa9d7d0107f9",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 86, 147, 21, 185, 39, 139, 185, 230, 86, 134, 240, 249, 157, 156, 79, 138, 161, 230, 15, 118, 212, 31, 174, 130, 182, 79, 141, 92, 115, 1, 112, 185, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}