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: fc56a0f31267eb140be4ff458568ea959db12cf93082abc8ac18405ea37bb7aa
Tx prefix hash: ab612b076ac5a7a65964e02a049a59a0f6d362f242a60e604619a59d1f2a32b4
Tx public key: 415c2f2724ef155bdc7683f166231129d92af008c64c4c1a35eb09ddb1f456c8
| Timestamp: 1779915426 | Timestamp [UTC]: 2026-05-27 20:57:06 | Age [y:d:h:m:s]: 00:012:20:11:57 |
| Block: 3294 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5440 | RingCT/type: yes/0 |
| Extra: 01415c2f2724ef155bdc7683f166231129d92af008c64c4c1a35eb09ddb1f456c802090000000126697be300 | ||
1 output(s) for total of 34.964074945980 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25d6286377cae3814ac08527eeb1b759f761513ec25d238abae355b312a668f2 | 34.964074945980 | 3956 of 0 | <93> |
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": 3354,
"vin": [ {
"gen": {
"height": 3294
}
}
],
"vout": [ {
"amount": 34964074945980,
"target": {
"tagged_key": {
"key": "25d6286377cae3814ac08527eeb1b759f761513ec25d238abae355b312a668f2",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 65, 92, 47, 39, 36, 239, 21, 91, 220, 118, 131, 241, 102, 35, 17, 41, 217, 42, 240, 8, 198, 76, 76, 26, 53, 235, 9, 221, 177, 244, 86, 200, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}