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: 629137fc05cb0e77c66c9a93146be44f50788d17050c05f511e0c8ee337b8471
Tx prefix hash: e5909c8ed9eab4d0af39f101eb600b782d8bc2a608646a7037a25cebbf8646ae
Tx public key: b9781574c198dfe05427e60c88c0770bb943337d9d5630d31a7ce80657bc417a
| Timestamp: 1780809260 | Timestamp [UTC]: 2026-06-07 05:14:20 | Age [y:d:h:m:s]: 00:001:20:21:37 |
| Block: 6997 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 889 | RingCT/type: yes/0 |
| Extra: 01b9781574c198dfe05427e60c88c0770bb943337d9d5630d31a7ce80657bc417a020900000001e49593ff00 | ||
1 output(s) for total of 34.717996565176 HMNY
| stealth address | amount | amount idx | tag |
| 00: 021bbda2bcfb0f088440e3840bbfc536453e0a6df2281cdf38fa86cf8d9ed70d | 34.717996565176 | 8629 of 0 | <f3> |
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": 7057,
"vin": [ {
"gen": {
"height": 6997
}
}
],
"vout": [ {
"amount": 34717996565176,
"target": {
"tagged_key": {
"key": "021bbda2bcfb0f088440e3840bbfc536453e0a6df2281cdf38fa86cf8d9ed70d",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 185, 120, 21, 116, 193, 152, 223, 224, 84, 39, 230, 12, 136, 192, 119, 11, 185, 67, 51, 125, 157, 86, 48, 211, 26, 124, 232, 6, 87, 188, 65, 122, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}