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: 96687caeb10fbc8886952134667c677fea93858887d684444d05dfe29cf5f50f
Tx prefix hash: c982297896b6c428d5ad0ac1dd9a98d4222a8388e715f858650ce97426314b43
Tx public key: 96e4153af08cee7eaa8e199798b783a74ee6d6a8becc651c9ffa1eb32576d986
| Timestamp: 1779724294 | Timestamp [UTC]: 2026-05-25 15:51:34 | Age [y:d:h:m:s]: 00:014:10:58:14 |
| Block: 1821 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6099 | RingCT/type: yes/0 |
| Extra: 0196e4153af08cee7eaa8e199798b783a74ee6d6a8becc651c9ffa1eb32576d986020900000003ba6d17be00 | ||
1 output(s) for total of 35.062445588898 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3993e384563691c6bdffa3f5460f7c674be9899e99278c74407dbad7ea74040 | 35.062445588898 | 2015 of 0 | <0f> |
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": 1881,
"vin": [ {
"gen": {
"height": 1821
}
}
],
"vout": [ {
"amount": 35062445588898,
"target": {
"tagged_key": {
"key": "b3993e384563691c6bdffa3f5460f7c674be9899e99278c74407dbad7ea74040",
"view_tag": "0f"
}
}
}
],
"extra": [ 1, 150, 228, 21, 58, 240, 140, 238, 126, 170, 142, 25, 151, 152, 183, 131, 167, 78, 230, 214, 168, 190, 204, 101, 28, 159, 250, 30, 179, 37, 118, 217, 134, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}