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: cda38b65a80ec66e39c2dd04173537b9a60db8c5b46c2cc7ca0a3bbbe7e9f113
Tx prefix hash: e53076e9567f70eb8ad99bc4f27476712c0efbe714ec1fb7ac07c1149e17446d
Tx public key: 660a7971d5b78f0ad97f940866a2343feea54881d84328ec33654cd5986e67a6
| Timestamp: 1780382248 | Timestamp [UTC]: 2026-06-02 06:37:28 | Age [y:d:h:m:s]: 00:011:04:43:37 |
| Block: 5154 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3591 | RingCT/type: yes/0 |
| Extra: 01660a7971d5b78f0ad97f940866a2343feea54881d84328ec33654cd5986e67a602090000000326697be300 | ||
1 output(s) for total of 34.970434450399 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2a26abfc63a4bc5df4da9372cb53e412501117df28f51058576efed19941637b | 34.970434450399 | 6529 of 0 | <5a> |
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": 5214,
"vin": [ {
"gen": {
"height": 5154
}
}
],
"vout": [ {
"amount": 34970434450399,
"target": {
"tagged_key": {
"key": "2a26abfc63a4bc5df4da9372cb53e412501117df28f51058576efed19941637b",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 102, 10, 121, 113, 213, 183, 143, 10, 217, 127, 148, 8, 102, 162, 52, 63, 238, 165, 72, 129, 216, 67, 40, 236, 51, 101, 76, 213, 152, 110, 103, 166, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}