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: e950bfb255ffc3e1f461a99b7bc5eaa2887101aedc0cc8b97d0555558e533f4a
Tx prefix hash: 7014ae75c02a4a34d9e68c880ea7209c0d64fec380ac3717f202d5720ee7bf7f
Tx public key: f5c1312fd24f743c6d5492db535c2347a99bca02ce4dc9c9bdc45443c20f160e
| Timestamp: 1779695075 | Timestamp [UTC]: 2026-05-25 07:44:35 | Age [y:d:h:m:s]: 00:014:19:05:13 |
| Block: 1540 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6379 | RingCT/type: yes/0 |
| Extra: 01f5c1312fd24f743c6d5492db535c2347a99bca02ce4dc9c9bdc45443c20f160e | ||
1 output(s) for total of 35.081242886173 HMNY
| stealth address | amount | amount idx | tag |
| 00: d04538901f4998dc202f7e1901c0dd40bd6be6ee33fba26b69af3cc7e4082502 | 35.081242886173 | 1698 of 0 | <df> |
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": 1600,
"vin": [ {
"gen": {
"height": 1540
}
}
],
"vout": [ {
"amount": 35081242886173,
"target": {
"tagged_key": {
"key": "d04538901f4998dc202f7e1901c0dd40bd6be6ee33fba26b69af3cc7e4082502",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 245, 193, 49, 47, 210, 79, 116, 60, 109, 84, 146, 219, 83, 92, 35, 71, 169, 155, 202, 2, 206, 77, 201, 201, 189, 196, 84, 67, 194, 15, 22, 14
],
"rct_signatures": {
"type": 0
}
}