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: 42efa0ee324b3405e8de24f30e5a1e000b29e4bc923096c9be2b9f295a3d96e7
Tx prefix hash: 37b985e93fd9690ebfc7a8068acd054d3b4a90575e8c6ba143dcdce854456d93
Tx public key: 707c74fe8ea7dbba99d7c6aab2857c1a7a1bfd51be1f1a478d0f251a13abc079
| Timestamp: 1779434207 | Timestamp [UTC]: 2026-05-22 07:16:47 | Age [y:d:h:m:s]: 00:017:18:19:10 |
| Block: 79 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7807 | RingCT/type: yes/0 |
| Extra: 01707c74fe8ea7dbba99d7c6aab2857c1a7a1bfd51be1f1a478d0f251a13abc079020900000001a662ed0300 | ||
1 output(s) for total of 35.179137981919 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f3d1349215a3904b125493b3e8146fb0805e2cec2a22926826b0a52e794484a | 35.179137981919 | 75 of 0 | <51> |
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": 139,
"vin": [ {
"gen": {
"height": 79
}
}
],
"vout": [ {
"amount": 35179137981919,
"target": {
"tagged_key": {
"key": "6f3d1349215a3904b125493b3e8146fb0805e2cec2a22926826b0a52e794484a",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 112, 124, 116, 254, 142, 167, 219, 186, 153, 215, 198, 170, 178, 133, 124, 26, 122, 27, 253, 81, 190, 31, 26, 71, 141, 15, 37, 26, 19, 171, 192, 121, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}