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: 6b322fb42fbf6ed2be8e63e0508c4f1d93f767fd9dc08d1be7930f980e2c5a46
Tx prefix hash: 8d371e70f9ffddeac0a668782a8ea85c9498c884381b7e3d060eb1f4b88e69e6
Tx public key: 4f4d9fc8b85373e7bac74c829f038acd9aea61c0b541e624472d99c8a1bfd9f6
| Timestamp: 1779457073 | Timestamp [UTC]: 2026-05-22 13:37:53 | Age [y:d:h:m:s]: 00:017:11:58:04 |
| Block: 397 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7489 | RingCT/type: yes/0 |
| Extra: 014f4d9fc8b85373e7bac74c829f038acd9aea61c0b541e624472d99c8a1bfd9f602090000000193369e7d00 | ||
1 output(s) for total of 35.157806987174 HMNY
| stealth address | amount | amount idx | tag |
| 00: be1e5bb17baf81b8b5fcd380a68e519ee7e13f6359721458b50a429cdddcf2f5 | 35.157806987174 | 397 of 0 | <b3> |
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": 457,
"vin": [ {
"gen": {
"height": 397
}
}
],
"vout": [ {
"amount": 35157806987174,
"target": {
"tagged_key": {
"key": "be1e5bb17baf81b8b5fcd380a68e519ee7e13f6359721458b50a429cdddcf2f5",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 79, 77, 159, 200, 184, 83, 115, 231, 186, 199, 76, 130, 159, 3, 138, 205, 154, 234, 97, 192, 181, 65, 230, 36, 71, 45, 153, 200, 161, 191, 217, 246, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}