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: a1777af603b3addcb6391eca836ddf76ecfcf0e43da768e11f9de569a13e9663
Tx prefix hash: 47d671b656288601a7b180e47b05392a557ec806cd66d258c9176bd5855ccb9f
Tx public key: 3d182dfa43d6d9fc98141b7c304d4d1ff3eba9cf4ab4d96152579e8063e330d9
| Timestamp: 1779950489 | Timestamp [UTC]: 2026-05-28 06:41:29 | Age [y:d:h:m:s]: 00:011:19:59:07 |
| Block: 3617 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4280 | RingCT/type: yes/0 |
| Extra: 013d182dfa43d6d9fc98141b7c304d4d1ff3eba9cf4ab4d96152579e8063e330d902090000000626697be300 | ||
1 output(s) for total of 34.942541115521 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2be9d0595cdb72996a69e50c648b4776ccf81b520fa79c2a502b9be0f283d633 | 34.942541115521 | 4368 of 0 | <63> |
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": 3677,
"vin": [ {
"gen": {
"height": 3617
}
}
],
"vout": [ {
"amount": 34942541115521,
"target": {
"tagged_key": {
"key": "2be9d0595cdb72996a69e50c648b4776ccf81b520fa79c2a502b9be0f283d633",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 61, 24, 45, 250, 67, 214, 217, 252, 152, 20, 27, 124, 48, 77, 77, 31, 243, 235, 169, 207, 74, 180, 217, 97, 82, 87, 158, 128, 99, 227, 48, 217, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}