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: 026a868fcc63ed558e463e02b6e11873ce629c7953c9234f57c97ffdb83f5517
Tx prefix hash: 35e25531a4ab566eefe2beb21357538d506cea13ed72e1d6938096f490fab288
Tx public key: c54eceb587a72352d42f671c99463a4d48cb44dbf5fdaa1b258a3a893b6706e7
| Timestamp: 1779957661 | Timestamp [UTC]: 2026-05-28 08:41:01 | Age [y:d:h:m:s]: 00:011:16:05:46 |
| Block: 3717 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4169 | RingCT/type: yes/0 |
| Extra: 01c54eceb587a72352d42f671c99463a4d48cb44dbf5fdaa1b258a3a893b6706e702090000000226697be300 | ||
1 output(s) for total of 34.935876983924 HMNY
| stealth address | amount | amount idx | tag |
| 00: 41ccacb6c8c2f7c6303e6297d8a031c5a33910962db20326276d5a6fe0d20d51 | 34.935876983924 | 4500 of 0 | <fb> |
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": 3777,
"vin": [ {
"gen": {
"height": 3717
}
}
],
"vout": [ {
"amount": 34935876983924,
"target": {
"tagged_key": {
"key": "41ccacb6c8c2f7c6303e6297d8a031c5a33910962db20326276d5a6fe0d20d51",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 197, 78, 206, 181, 135, 167, 35, 82, 212, 47, 103, 28, 153, 70, 58, 77, 72, 203, 68, 219, 245, 253, 170, 27, 37, 138, 58, 137, 59, 103, 6, 231, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}