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: 5172c7f6c42607b6c186450f4e06e101edb5e8fe14efd62aeb61f9fa0eabd8fd
Tx prefix hash: e5ff1cd69668de4dd2485194901d61b3b0a7d4ef312175bfcf3cdfefb95efaa0
Tx public key: 7521b39fcb140c9875ff74c9e911ca88184fc20e508ac4f7358e07e1d5448be9
| Timestamp: 1780802634 | Timestamp [UTC]: 2026-06-07 03:23:54 | Age [y:d:h:m:s]: 00:001:22:12:03 |
| Block: 6869 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1017 | RingCT/type: yes/0 |
| Extra: 017521b39fcb140c9875ff74c9e911ca88184fc20e508ac4f7358e07e1d5448be9020900000001e49593ff00 | ||
1 output(s) for total of 34.726473681403 HMNY
| stealth address | amount | amount idx | tag |
| 00: ed43f49dc47b79e42fa6348ad0228c01e4dc8f4f4717f6e080f3dcb9f0b55bf7 | 34.726473681403 | 8479 of 0 | <eb> |
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": 6929,
"vin": [ {
"gen": {
"height": 6869
}
}
],
"vout": [ {
"amount": 34726473681403,
"target": {
"tagged_key": {
"key": "ed43f49dc47b79e42fa6348ad0228c01e4dc8f4f4717f6e080f3dcb9f0b55bf7",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 117, 33, 179, 159, 203, 20, 12, 152, 117, 255, 116, 201, 233, 17, 202, 136, 24, 79, 194, 14, 80, 138, 196, 247, 53, 142, 7, 225, 213, 68, 139, 233, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}