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: eb2daf467fc3954729abddcefdb7c04f111731ec25e9bccbb8744bd3d6058702
Tx prefix hash: 7477c2e9c771a5ba065786e6e4b218d1bfe616b7dc9e738fdbb0a461e70575d7
Tx public key: abf2f5c7b5a4e23e0c76f163c7864f50dbdc83b8fda96122fdf8bce2b6f5ff06
| Timestamp: 1780815352 | Timestamp [UTC]: 2026-06-07 06:55:52 | Age [y:d:h:m:s]: 00:010:01:33:20 |
| Block: 7058 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1687 | RingCT/type: yes/0 |
| Extra: 01abf2f5c7b5a4e23e0c76f163c7864f50dbdc83b8fda96122fdf8bce2b6f5ff06020900000004e49593ff00 | ||
1 output(s) for total of 34.713957417582 HMNY
| stealth address | amount | amount idx | tag |
| 00: a18253ff1d384b4e5f0201c53f023db62c5aaec77e36edd182622d96f97ef9b4 | 34.713957417582 | 8702 of 0 | <65> |
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": 7118,
"vin": [ {
"gen": {
"height": 7058
}
}
],
"vout": [ {
"amount": 34713957417582,
"target": {
"tagged_key": {
"key": "a18253ff1d384b4e5f0201c53f023db62c5aaec77e36edd182622d96f97ef9b4",
"view_tag": "65"
}
}
}
],
"extra": [ 1, 171, 242, 245, 199, 181, 164, 226, 62, 12, 118, 241, 99, 199, 134, 79, 80, 219, 220, 131, 184, 253, 169, 97, 34, 253, 248, 188, 226, 182, 245, 255, 6, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}