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: cf5099681ebed6451e4264e3ab65695c41156151639b15f7f7001646e14bda03
Tx prefix hash: 83896ce6800b349c20b0ec6ecd0577206b93b6ef702d1d413c5b3af421ecd51b
Tx public key: d637e26df175ed44622643a09f92da95df20fd8b698d03b0c87a6b5efaefba20
| Timestamp: 1779433789 | Timestamp [UTC]: 2026-05-22 07:09:49 | Age [y:d:h:m:s]: 00:017:20:41:09 |
| Block: 63 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7904 | RingCT/type: yes/0 |
| Extra: 01d637e26df175ed44622643a09f92da95df20fd8b698d03b0c87a6b5efaefba20020900000001a662ed0300 | ||
1 output(s) for total of 35.180211581416 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2a13a04fcb1e158f50f822bd18022256cb94d7d8556433a7694ab8c006a6e248 | 35.180211581416 | 59 of 0 | <5c> |
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": 123,
"vin": [ {
"gen": {
"height": 63
}
}
],
"vout": [ {
"amount": 35180211581416,
"target": {
"tagged_key": {
"key": "2a13a04fcb1e158f50f822bd18022256cb94d7d8556433a7694ab8c006a6e248",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 214, 55, 226, 109, 241, 117, 237, 68, 98, 38, 67, 160, 159, 146, 218, 149, 223, 32, 253, 139, 105, 141, 3, 176, 200, 122, 107, 94, 250, 239, 186, 32, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}