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: f1c7c25d8425c9197b4c7a3598c3ee9ec738bc4a4a26129339e2f9f98a623f79
Tx prefix hash: 0e13a48edb662969b6ebc5dc54fadff55b98b74d7c5f852aabf8277b8d141e47
Tx public key: ba53514cf25cf63c5a3877b41deeb81b2f60d8bb7ae6b44b7d5ada1d9c0a8b44
| Timestamp: 1780316084 | Timestamp [UTC]: 2026-06-01 12:14:44 | Age [y:d:h:m:s]: 00:007:13:21:13 |
| Block: 5002 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2884 | RingCT/type: yes/0 |
| Extra: 01ba53514cf25cf63c5a3877b41deeb81b2f60d8bb7ae6b44b7d5ada1d9c0a8b4402090000000126697be300 | ||
1 output(s) for total of 34.850355905916 HMNY
| stealth address | amount | amount idx | tag |
| 00: 88549a96e08ab882aaccefd409cad3f9c30a5be3adbe62c962338247752f3e9a | 34.850355905916 | 6373 of 0 | <0e> |
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": 5062,
"vin": [ {
"gen": {
"height": 5002
}
}
],
"vout": [ {
"amount": 34850355905916,
"target": {
"tagged_key": {
"key": "88549a96e08ab882aaccefd409cad3f9c30a5be3adbe62c962338247752f3e9a",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 186, 83, 81, 76, 242, 92, 246, 60, 90, 56, 119, 180, 29, 238, 184, 27, 47, 96, 216, 187, 122, 230, 180, 75, 125, 90, 218, 29, 156, 10, 139, 68, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}