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: 3e543fb09a3c4860a4dcde415141c0706e92bef86f778b8b9a371fa53fcaeb70
Tx prefix hash: c9dc24bcf213611c7d837b7b21130fe5f15dbf0046f9e2882a4a59eb32a0adfc
Tx public key: 4070601471f469e74428ea3f2bfde41f1a487c9c8fabcde33aebf6bdea483e21
| Timestamp: 1779708972 | Timestamp [UTC]: 2026-05-25 11:36:12 | Age [y:d:h:m:s]: 00:014:15:13:36 |
| Block: 1573 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6347 | RingCT/type: yes/0 |
| Extra: 014070601471f469e74428ea3f2bfde41f1a487c9c8fabcde33aebf6bdea483e21020900000002ba6d17be00 | ||
1 output(s) for total of 35.079034852255 HMNY
| stealth address | amount | amount idx | tag |
| 00: d951b2a69fd8f7fb5ac1c12407e34f28fcbd0f9d88709a4e1e4d52572264e0c3 | 35.079034852255 | 1731 of 0 | <bb> |
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": 1633,
"vin": [ {
"gen": {
"height": 1573
}
}
],
"vout": [ {
"amount": 35079034852255,
"target": {
"tagged_key": {
"key": "d951b2a69fd8f7fb5ac1c12407e34f28fcbd0f9d88709a4e1e4d52572264e0c3",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 64, 112, 96, 20, 113, 244, 105, 231, 68, 40, 234, 63, 43, 253, 228, 31, 26, 72, 124, 156, 143, 171, 205, 227, 58, 235, 246, 189, 234, 72, 62, 33, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}