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: d4ad45db32c0283890e895ecd7e8ca2f2e57ed87f6c381505e7f013d0e3fcdd6
Tx prefix hash: 11a3403dbdcd260b374b50a5087d4d7cf25a824c02209e104bc2ee9987ad84b4
Tx public key: 2b2074da3c53c8aea1e75a8a3b7433ba5658efa4547b2a89d12a6f6a40de322a
| Timestamp: 1779461772 | Timestamp [UTC]: 2026-05-22 14:56:12 | Age [y:d:h:m:s]: 00:017:10:39:45 |
| Block: 450 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7436 | RingCT/type: yes/0 |
| Extra: 012b2074da3c53c8aea1e75a8a3b7433ba5658efa4547b2a89d12a6f6a40de322a02090000000293369e7d00 | ||
1 output(s) for total of 35.154253079079 HMNY
| stealth address | amount | amount idx | tag |
| 00: f126c3a6c1106f2c3aae7e1240ac4b20a2e4579dea700aed3e5dafa2467c768f | 35.154253079079 | 454 of 0 | <28> |
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": 510,
"vin": [ {
"gen": {
"height": 450
}
}
],
"vout": [ {
"amount": 35154253079079,
"target": {
"tagged_key": {
"key": "f126c3a6c1106f2c3aae7e1240ac4b20a2e4579dea700aed3e5dafa2467c768f",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 43, 32, 116, 218, 60, 83, 200, 174, 161, 231, 90, 138, 59, 116, 51, 186, 86, 88, 239, 164, 84, 123, 42, 137, 209, 42, 111, 106, 64, 222, 50, 42, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}