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: 2baa0ec4a4b674591aeadeb5f74ecf842ea02a8fa68667dd1581c62b4980ba23
Tx prefix hash: 56704a99de3c196353150d5ec2f936e0b2a94e7c4f531f218ce7857323a3b26c
Tx public key: dd74a8f2b5cb74cb8335af92f44018af5aaeb5934614e3387d4ef4da4b4c1213
| Timestamp: 1780705573 | Timestamp [UTC]: 2026-06-06 00:26:13 | Age [y:d:h:m:s]: 00:011:07:39:08 |
| Block: 6104 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2641 | RingCT/type: yes/0 |
| Extra: 01dd74a8f2b5cb74cb8335af92f44018af5aaeb5934614e3387d4ef4da4b4c1213020900000003e49593ff00 | ||
1 output(s) for total of 34.777180866197 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64810347a1b72b2a13fe902612b3dfc9d75ab41836d8c386298a3853f52e6746 | 34.777180866197 | 7577 of 0 | <9d> |
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": 6164,
"vin": [ {
"gen": {
"height": 6104
}
}
],
"vout": [ {
"amount": 34777180866197,
"target": {
"tagged_key": {
"key": "64810347a1b72b2a13fe902612b3dfc9d75ab41836d8c386298a3853f52e6746",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 221, 116, 168, 242, 181, 203, 116, 203, 131, 53, 175, 146, 244, 64, 24, 175, 90, 174, 181, 147, 70, 20, 227, 56, 125, 78, 244, 218, 75, 76, 18, 19, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}