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: 351c50d286221093bb1464014d2b937a815f529b039e6d546bf7b3858e7a39ad
Tx prefix hash: c4004542ff77aa034dbaa1b196af519ed75950462cc9af2689085ee4b17e15d4
Tx public key: af4636b65b112357fe413ccf87850a9838ac2aeab9a7ef629bc0ad084857522e
| Timestamp: 1780771424 | Timestamp [UTC]: 2026-06-06 18:43:44 | Age [y:d:h:m:s]: 00:002:06:03:03 |
| Block: 6669 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1217 | RingCT/type: yes/0 |
| Extra: 01af4636b65b112357fe413ccf87850a9838ac2aeab9a7ef629bc0ad084857522e020900000001e49593ff00 | ||
1 output(s) for total of 34.739723319465 HMNY
| stealth address | amount | amount idx | tag |
| 00: 828d6c85582c61e19f1770c617328f1a1dcdd1015742034e27359cdbbab4ef35 | 34.739723319465 | 8225 of 0 | <31> |
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": 6729,
"vin": [ {
"gen": {
"height": 6669
}
}
],
"vout": [ {
"amount": 34739723319465,
"target": {
"tagged_key": {
"key": "828d6c85582c61e19f1770c617328f1a1dcdd1015742034e27359cdbbab4ef35",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 175, 70, 54, 182, 91, 17, 35, 87, 254, 65, 60, 207, 135, 133, 10, 152, 56, 172, 42, 234, 185, 167, 239, 98, 155, 192, 173, 8, 72, 87, 82, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}