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: e09ab14185cb40a0018928193afdb8107def0957d4c25737ab3cba616a648e29
Tx prefix hash: 1e6651a2e049c81708bdb1acd2e8f4c83523ecc09279c3bb37402b7728dbc05d
Tx public key: e0cd5808698735f1fdfa1b3c48b850adf1e5e5392a564380a93fb3e743582fb5
| Timestamp: 1779786629 | Timestamp [UTC]: 2026-05-26 09:10:29 | Age [y:d:h:m:s]: 00:013:14:08:24 |
| Block: 2171 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5715 | RingCT/type: yes/0 |
| Extra: 01e0cd5808698735f1fdfa1b3c48b850adf1e5e5392a564380a93fb3e743582fb502090000000126697be300 | ||
1 output(s) for total of 35.046435070004 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4108b2ff8dc701e73b3c6ae24b4feba5ee487d92ebf69066910497cd2fe5f68a | 35.046435070004 | 2507 of 0 | <45> |
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": 2231,
"vin": [ {
"gen": {
"height": 2171
}
}
],
"vout": [ {
"amount": 35046435070004,
"target": {
"tagged_key": {
"key": "4108b2ff8dc701e73b3c6ae24b4feba5ee487d92ebf69066910497cd2fe5f68a",
"view_tag": "45"
}
}
}
],
"extra": [ 1, 224, 205, 88, 8, 105, 135, 53, 241, 253, 250, 27, 60, 72, 184, 80, 173, 241, 229, 229, 57, 42, 86, 67, 128, 169, 63, 179, 231, 67, 88, 47, 181, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}