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: 80bb190aa6076b506ca83a01393067e982cacdfe55314b3523f5e078eed7810d
Tx prefix hash: e83f573930cf34050fea9edcce914f0786123f1aee323641e76f9a21c53d349b
Tx public key: 48a6c9084a2f37d6d83d2ce278cdf239f7df14b061225233476aaafc4458d356
| Timestamp: 1780996433 | Timestamp [UTC]: 2026-06-09 09:13:53 | Age [y:d:h:m:s]: 00:007:22:51:28 |
| Block: 8346 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 399 | RingCT/type: yes/0 |
| Extra: 0148a6c9084a2f37d6d83d2ce278cdf239f7df14b061225233476aaafc4458d356020900000001e49593ff00 | ||
1 output(s) for total of 34.628781438060 HMNY
| stealth address | amount | amount idx | tag |
| 00: dab7cd053a637d7d9d2c42f632c1aa7d478e02e1cb8904a76a49bc17858ae6cc | 34.628781438060 | 10322 of 0 | <8a> |
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": 8406,
"vin": [ {
"gen": {
"height": 8346
}
}
],
"vout": [ {
"amount": 34628781438060,
"target": {
"tagged_key": {
"key": "dab7cd053a637d7d9d2c42f632c1aa7d478e02e1cb8904a76a49bc17858ae6cc",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 72, 166, 201, 8, 74, 47, 55, 214, 216, 61, 44, 226, 120, 205, 242, 57, 247, 223, 20, 176, 97, 34, 82, 51, 71, 106, 170, 252, 68, 88, 211, 86, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}