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: fc589488b23dba8c6d715da4d37ad577bfa86cd81db26b1f4f5e41f4efefd6cd
Tx prefix hash: 3405c5bfa4bcfdcd45b2652075537fe75eaa0072b2399577f6c2ba6ea21cf9bf
Tx public key: db41a2b7a99d56222e422aca58dad8a574b326442d3ed205954241d58c700d60
| Timestamp: 1779775209 | Timestamp [UTC]: 2026-05-26 06:00:09 | Age [y:d:h:m:s]: 00:022:02:36:05 |
| Block: 2059 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6686 | RingCT/type: yes/0 |
| Extra: 01db41a2b7a99d56222e422aca58dad8a574b326442d3ed205954241d58c700d6002090000000226697be300 | ||
1 output(s) for total of 35.046532624610 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43bec37b568ea2297e06fccb4a07b84681d2fb1a36d167e6abe41a4c288244a2 | 35.046532624610 | 2359 of 0 | <29> |
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": 2119,
"vin": [ {
"gen": {
"height": 2059
}
}
],
"vout": [ {
"amount": 35046532624610,
"target": {
"tagged_key": {
"key": "43bec37b568ea2297e06fccb4a07b84681d2fb1a36d167e6abe41a4c288244a2",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 219, 65, 162, 183, 169, 157, 86, 34, 46, 66, 42, 202, 88, 218, 216, 165, 116, 179, 38, 68, 45, 62, 210, 5, 149, 66, 65, 213, 140, 112, 13, 96, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}