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: f1d1d3830f91e1879a6d2e9c6ab5cbe18f69651b7f6d69a2c1ef6172214de5b5
Tx prefix hash: 0ad5d00a9a13ea3f9832c1aa167a6494077da4f13cb0f3633004989ff08308fd
Tx public key: e3dc00eba7cd292802c051a9055d77c316ea52413a2466aae2571b02b4f0356f
| Timestamp: 1779938373 | Timestamp [UTC]: 2026-05-28 03:19:33 | Age [y:d:h:m:s]: 00:011:22:16:24 |
| Block: 3458 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4428 | RingCT/type: yes/0 |
| Extra: 01e3dc00eba7cd292802c051a9055d77c316ea52413a2466aae2571b02b4f0356f02090000000126697be300 | ||
1 output(s) for total of 34.953139702331 HMNY
| stealth address | amount | amount idx | tag |
| 00: e3205c36746059e8dd5a6a4c3187572050beaf74e549f145c6a563dae4d6ea7d | 34.953139702331 | 4175 of 0 | <2b> |
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": 3518,
"vin": [ {
"gen": {
"height": 3458
}
}
],
"vout": [ {
"amount": 34953139702331,
"target": {
"tagged_key": {
"key": "e3205c36746059e8dd5a6a4c3187572050beaf74e549f145c6a563dae4d6ea7d",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 227, 220, 0, 235, 167, 205, 41, 40, 2, 192, 81, 169, 5, 93, 119, 195, 22, 234, 82, 65, 58, 36, 102, 170, 226, 87, 27, 2, 180, 240, 53, 111, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}