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: b878bff7c73f3e41f413c64a3ba45107b9a98d4984188e83b8a5ef521dd698bc
Tx prefix hash: c445972aeba173155825a47c353dea32cbf9a6408c337ab1112bb3a6a6dbb4ce
Tx public key: a7febaf134bfd6c54c07db044636b68b1f07ba76d09c814ea09adc06b423975e
| Timestamp: 1780986049 | Timestamp [UTC]: 2026-06-09 06:20:49 | Age [y:d:h:m:s]: 00:000:09:38:55 |
| Block: 8142 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 549 | RingCT/type: yes/0 |
| Extra: 01a7febaf134bfd6c54c07db044636b68b1f07ba76d09c814ea09adc06b423975e020900000002e49593ff00 | ||
1 output(s) for total of 34.642258101043 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a4cfa93bd31083a07cc8770b2ec06f101c35ad8725bf4376557872c60a2a9f3 | 34.642258101043 | 10084 of 0 | <41> |
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": 8202,
"vin": [ {
"gen": {
"height": 8142
}
}
],
"vout": [ {
"amount": 34642258101043,
"target": {
"tagged_key": {
"key": "3a4cfa93bd31083a07cc8770b2ec06f101c35ad8725bf4376557872c60a2a9f3",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 167, 254, 186, 241, 52, 191, 214, 197, 76, 7, 219, 4, 70, 54, 182, 139, 31, 7, 186, 118, 208, 156, 129, 78, 160, 154, 220, 6, 180, 35, 151, 94, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}