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: 41ccd110ea0845d5596ec834bdbf8fc6042b596fe447ad65e2cbca9e8680e7bd
Tx prefix hash: a8b1979114de89c0ced89ca5fe3115ac66e98bc4ed9d2a64d0aacb37a45e5643
Tx public key: 56632cbc17f7a59be1272fa8f7a7efd3d2d9a518fc250329b2d4d9fbd32b4343
| Timestamp: 1779638666 | Timestamp [UTC]: 2026-05-24 16:04:26 | Age [y:d:h:m:s]: 00:021:16:15:09 |
| Block: 1207 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7538 | RingCT/type: yes/0 |
| Extra: 0156632cbc17f7a59be1272fa8f7a7efd3d2d9a518fc250329b2d4d9fbd32b4343020900000001ba6d17be00 | ||
1 output(s) for total of 35.103531734527 HMNY
| stealth address | amount | amount idx | tag |
| 00: 440ee4d5f6cf99666ec99dbf4223f76b24923f31ba4c95fe26cbeaf62ba1019a | 35.103531734527 | 1351 of 0 | <0b> |
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": 1267,
"vin": [ {
"gen": {
"height": 1207
}
}
],
"vout": [ {
"amount": 35103531734527,
"target": {
"tagged_key": {
"key": "440ee4d5f6cf99666ec99dbf4223f76b24923f31ba4c95fe26cbeaf62ba1019a",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 86, 99, 44, 188, 23, 247, 165, 155, 225, 39, 47, 168, 247, 167, 239, 211, 210, 217, 165, 24, 252, 37, 3, 41, 178, 212, 217, 251, 211, 43, 67, 67, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}