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: a66c515679c8764c0f3c28e0e8b55eaef6193f3db49dffe9e0bb8379a2ada69b
Tx prefix hash: 18f67a2c0e03ff903b6b2f9bb7ce3cc15739bc8f211312236da08b73d16efd32
Tx public key: 923d3511c9a2f5a0804b3a1f3bd442bd305aa5bbd6d3be23b9fd6fa9573bf024
| Timestamp: 1779647075 | Timestamp [UTC]: 2026-05-24 18:24:35 | Age [y:d:h:m:s]: 00:023:13:40:46 |
| Block: 1455 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7290 | RingCT/type: yes/0 |
| Extra: 01923d3511c9a2f5a0804b3a1f3bd442bd305aa5bbd6d3be23b9fd6fa9573bf024 | ||
1 output(s) for total of 35.086930886323 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e58e0e905da44bf3a69054a676ec95a5ef81f1a64372909ac9b6e78db085f98 | 35.086930886323 | 1609 of 0 | <8d> |
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": 1515,
"vin": [ {
"gen": {
"height": 1455
}
}
],
"vout": [ {
"amount": 35086930886323,
"target": {
"tagged_key": {
"key": "4e58e0e905da44bf3a69054a676ec95a5ef81f1a64372909ac9b6e78db085f98",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 146, 61, 53, 17, 201, 162, 245, 160, 128, 75, 58, 31, 59, 212, 66, 189, 48, 90, 165, 187, 214, 211, 190, 35, 185, 253, 111, 169, 87, 59, 240, 36
],
"rct_signatures": {
"type": 0
}
}