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: b6cee1248217c691c7e3b352891ab963408736ec379c8c381d9c70e5c696448d
Tx prefix hash: 459ae00c3e3ba8efc8f67eaec7607c94d8c7ebb003941ed7c3039b2fc058497d
Tx public key: 1ea4e16494c5b4a0769cd69114ed7a1f51235eea0379727e806204620ff482d8
| Timestamp: 1780990189 | Timestamp [UTC]: 2026-06-09 07:29:49 | Age [y:d:h:m:s]: 00:000:08:29:55 |
| Block: 8216 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 475 | RingCT/type: yes/0 |
| Extra: 011ea4e16494c5b4a0769cd69114ed7a1f51235eea0379727e806204620ff482d8020900000001e49593ff00 | ||
1 output(s) for total of 34.637368901520 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7cf4988024399e66cd3d087a171b578d065e66a91361867fb7b174c8f2ca6863 | 34.637368901520 | 10172 of 0 | <6a> |
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": 8276,
"vin": [ {
"gen": {
"height": 8216
}
}
],
"vout": [ {
"amount": 34637368901520,
"target": {
"tagged_key": {
"key": "7cf4988024399e66cd3d087a171b578d065e66a91361867fb7b174c8f2ca6863",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 30, 164, 225, 100, 148, 197, 180, 160, 118, 156, 214, 145, 20, 237, 122, 31, 81, 35, 94, 234, 3, 121, 114, 126, 128, 98, 4, 98, 15, 244, 130, 216, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}