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: f26c0a864ec0d81e3373de0609d360aca61d50e54ea1d9a36660e10dcc8990a5
Tx prefix hash: 20f9b58d04b9e0dcacf21634c5b83cb924a4e1e1d181a08dc8f509b1ad1634fb
Tx public key: aad58a4f0ae075f4091fcbe3e0201b153843e350912a2a805484d0d446f399f8
| Timestamp: 1779933675 | Timestamp [UTC]: 2026-05-28 02:01:15 | Age [y:d:h:m:s]: 00:011:23:34:42 |
| Block: 3421 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4465 | RingCT/type: yes/0 |
| Extra: 01aad58a4f0ae075f4091fcbe3e0201b153843e350912a2a805484d0d446f399f802090000000126697be300 | ||
1 output(s) for total of 34.955606501185 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4271aa6842359a5bdf23c2ec1d4aa56273f3b8f4eef89d18b7c2096c7ab26405 | 34.955606501185 | 4136 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": 3481,
"vin": [ {
"gen": {
"height": 3421
}
}
],
"vout": [ {
"amount": 34955606501185,
"target": {
"tagged_key": {
"key": "4271aa6842359a5bdf23c2ec1d4aa56273f3b8f4eef89d18b7c2096c7ab26405",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 170, 213, 138, 79, 10, 224, 117, 244, 9, 31, 203, 227, 224, 32, 27, 21, 56, 67, 227, 80, 145, 42, 42, 128, 84, 132, 208, 212, 70, 243, 153, 248, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}