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: 28711e053ee06cb675a699a4660c5b056625beaa8498a9bc095f0d3925f40762
Tx prefix hash: a737186ec180d7358f1a878bdd699e8ea9b7e16845c1c44c6a6c6b95b982ba51
Tx public key: 5a0fa9c3f841d0c2c783aa359bc9eefc803f166131b1746c7eb87e96df396aa5
| Timestamp: 1779974128 | Timestamp [UTC]: 2026-05-28 13:15:28 | Age [y:d:h:m:s]: 00:011:14:35:30 |
| Block: 3873 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4082 | RingCT/type: yes/0 |
| Extra: 015a0fa9c3f841d0c2c783aa359bc9eefc803f166131b1746c7eb87e96df396aa502090000000326697be300 | ||
1 output(s) for total of 34.925483476401 HMNY
| stealth address | amount | amount idx | tag |
| 00: bfba91418e1e842e7e8bd4d6a93aa42932adc52d39fd9181c9dc62a94900a6fe | 34.925483476401 | 4735 of 0 | <3f> |
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": 3933,
"vin": [ {
"gen": {
"height": 3873
}
}
],
"vout": [ {
"amount": 34925483476401,
"target": {
"tagged_key": {
"key": "bfba91418e1e842e7e8bd4d6a93aa42932adc52d39fd9181c9dc62a94900a6fe",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 90, 15, 169, 195, 248, 65, 208, 194, 199, 131, 170, 53, 155, 201, 238, 252, 128, 63, 22, 97, 49, 177, 116, 108, 126, 184, 126, 150, 223, 57, 106, 165, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}