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: 40dff2fb92ef9921490e0fc9d9cc8015287955b67d050c077bfac4b1c0a3e865
Tx prefix hash: 141978fc15278b7b6e137fa217672d9d8d12d4cde22ff2e338811932a812f2cd
Tx public key: 572af6dd9ad0c353abc4d772c61704ebde27d86c45bc4398d8e0d3142c2f6325
| Timestamp: 1779845825 | Timestamp [UTC]: 2026-05-27 01:37:05 | Age [y:d:h:m:s]: 00:012:23:58:52 |
| Block: 2448 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5438 | RingCT/type: yes/0 |
| Extra: 01572af6dd9ad0c353abc4d772c61704ebde27d86c45bc4398d8e0d3142c2f632502090000000226697be300 | ||
1 output(s) for total of 35.020539167130 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b4018afb0228a44519402d329ca04f757154c16c188d2e94e1fee1be62c7fff | 35.020539167130 | 2878 of 0 | <da> |
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": 2508,
"vin": [ {
"gen": {
"height": 2448
}
}
],
"vout": [ {
"amount": 35020539167130,
"target": {
"tagged_key": {
"key": "1b4018afb0228a44519402d329ca04f757154c16c188d2e94e1fee1be62c7fff",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 87, 42, 246, 221, 154, 208, 195, 83, 171, 196, 215, 114, 198, 23, 4, 235, 222, 39, 216, 108, 69, 188, 67, 152, 216, 224, 211, 20, 44, 47, 99, 37, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}