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: c7b600c4b87b1d152b8968fa528590f45259cba27ddf27f8665f083da8b3e60e
Tx prefix hash: 9dc23a0ce2a90df85d7631a7cba7a7b1284dbf5073e62a7e3fa8f9072eeb7bf6
Tx public key: 4ed1a3c544e67c6299021ab43eade97a0d67bde1fd2ac40585915d2d9051ecf0
| Timestamp: 1780064794 | Timestamp [UTC]: 2026-05-29 14:26:34 | Age [y:d:h:m:s]: 00:010:11:09:23 |
| Block: 4570 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3316 | RingCT/type: yes/0 |
| Extra: 014ed1a3c544e67c6299021ab43eade97a0d67bde1fd2ac40585915d2d9051ecf002090000000226697be300 | ||
1 output(s) for total of 34.879083575517 HMNY
| stealth address | amount | amount idx | tag |
| 00: 19aab91a5b4f708a3c79d2b14526c27c7d4d2ccc6948bf994f67e23807bdf792 | 34.879083575517 | 5736 of 0 | <6d> |
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": 4630,
"vin": [ {
"gen": {
"height": 4570
}
}
],
"vout": [ {
"amount": 34879083575517,
"target": {
"tagged_key": {
"key": "19aab91a5b4f708a3c79d2b14526c27c7d4d2ccc6948bf994f67e23807bdf792",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 78, 209, 163, 197, 68, 230, 124, 98, 153, 2, 26, 180, 62, 173, 233, 122, 13, 103, 189, 225, 253, 42, 196, 5, 133, 145, 93, 45, 144, 81, 236, 240, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}