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: 1a6d7c2c67e154e67be6607800b2d89aacc8861a23c82d407157141dbacc20fe
Tx prefix hash: b35b52e054e4b6512265d88baae763dcd2ed42a0369a44600d91e4a7419dd13a
Tx public key: e50ccad092bd8d20df548c713e12c1415ca4600eb917c9d9deb66aa5bf189abb
| Timestamp: 1780014348 | Timestamp [UTC]: 2026-05-29 00:25:48 | Age [y:d:h:m:s]: 00:010:22:53:05 |
| Block: 4111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3775 | RingCT/type: yes/0 |
| Extra: 01e50ccad092bd8d20df548c713e12c1415ca4600eb917c9d9deb66aa5bf189abb02090000000126697be300 | ||
1 output(s) for total of 34.909632671873 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3849c8b7ea4ab07e227df5497594b8447e96abd56c783b5f04f55af3e9348a9c | 34.909632671873 | 5124 of 0 | <48> |
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": 4171,
"vin": [ {
"gen": {
"height": 4111
}
}
],
"vout": [ {
"amount": 34909632671873,
"target": {
"tagged_key": {
"key": "3849c8b7ea4ab07e227df5497594b8447e96abd56c783b5f04f55af3e9348a9c",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 229, 12, 202, 208, 146, 189, 141, 32, 223, 84, 140, 113, 62, 18, 193, 65, 92, 164, 96, 14, 185, 23, 201, 217, 222, 182, 106, 165, 191, 24, 154, 187, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}