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: b36dc9f2c0e5c65a22ba7ca35540374574d0afbfad922480b1054aaa398a2adf
Tx prefix hash: 9a66054477aa858e94fcfdf09d6f0d771ecb840beb8cda282cfb5dfe9679c664
Tx public key: ac308a3db6e7aa33223218d03a15796c575ef0f913c9c86d70a18e4d04129760
| Timestamp: 1779883479 | Timestamp [UTC]: 2026-05-27 12:04:39 | Age [y:d:h:m:s]: 00:012:13:31:18 |
| Block: 2982 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4904 | RingCT/type: yes/0 |
| Extra: 01ac308a3db6e7aa33223218d03a15796c575ef0f913c9c86d70a18e4d0412976002090000000126697be300 | ||
1 output(s) for total of 34.984888026402 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b019447aed6de5576601e2a542f0a49eaa9b4cc2adc880abb194ecd17430420 | 34.984888026402 | 3538 of 0 | <e0> |
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": 3042,
"vin": [ {
"gen": {
"height": 2982
}
}
],
"vout": [ {
"amount": 34984888026402,
"target": {
"tagged_key": {
"key": "3b019447aed6de5576601e2a542f0a49eaa9b4cc2adc880abb194ecd17430420",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 172, 48, 138, 61, 182, 231, 170, 51, 34, 50, 24, 208, 58, 21, 121, 108, 87, 94, 240, 249, 19, 201, 200, 109, 112, 161, 142, 77, 4, 18, 151, 96, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}