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: 0e138da855acb15a17f04a79304b7e4ac1bfdc50ae5d0512c3f3bb1ed3524a5f
Tx prefix hash: 1054c6c656a75acf71542d1865f4b4b667cf1dcf4fe9ca8bb99107d4c26ec7e2
Tx public key: e9e67e739283001a99e3e701e9db083481d778df9faa33a6fafbf274a1e99626
| Timestamp: 1779854008 | Timestamp [UTC]: 2026-05-27 03:53:28 | Age [y:d:h:m:s]: 00:012:19:25:25 |
| Block: 2584 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5302 | RingCT/type: yes/0 |
| Extra: 01e9e67e739283001a99e3e701e9db083481d778df9faa33a6fafbf274a1e9962602090000000126697be300 | ||
1 output(s) for total of 35.011456029259 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f69263fce3dc2aeb52f50c8f9c9351f40383f36a1a55b50905694b803fc4ca1 | 35.011456029259 | 3042 of 0 | <96> |
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": 2644,
"vin": [ {
"gen": {
"height": 2584
}
}
],
"vout": [ {
"amount": 35011456029259,
"target": {
"tagged_key": {
"key": "7f69263fce3dc2aeb52f50c8f9c9351f40383f36a1a55b50905694b803fc4ca1",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 233, 230, 126, 115, 146, 131, 0, 26, 153, 227, 231, 1, 233, 219, 8, 52, 129, 215, 120, 223, 159, 170, 51, 166, 250, 251, 242, 116, 161, 233, 150, 38, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}