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: a825a7671f94d6e37fd1dc146e6e10ad91f0bb9ef7d4582e68c9f66e9cf7a9aa
Tx prefix hash: b40fa7fe34f66bd86c999ff1f412f2a0d9d0af7573a268316c635779f820d876
Tx public key: 04756998300560e174c1d3fb4c3b102c562cda6bab71c125c6d8e51ee4d8f9f8
| Timestamp: 1781016780 | Timestamp [UTC]: 2026-06-09 14:53:00 | Age [y:d:h:m:s]: 00:006:01:50:14 |
| Block: 8640 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 105 | RingCT/type: yes/0 |
| Extra: 0104756998300560e174c1d3fb4c3b102c562cda6bab71c125c6d8e51ee4d8f9f8020900000001e49593ff00 | ||
1 output(s) for total of 34.609368410359 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61d656d41ab6d6863634c24e64b211ee58f2f6ead69b47deaa53dbb3c643ed0e | 34.609368410359 | 10682 of 0 | <fa> |
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": 8700,
"vin": [ {
"gen": {
"height": 8640
}
}
],
"vout": [ {
"amount": 34609368410359,
"target": {
"tagged_key": {
"key": "61d656d41ab6d6863634c24e64b211ee58f2f6ead69b47deaa53dbb3c643ed0e",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 4, 117, 105, 152, 48, 5, 96, 225, 116, 193, 211, 251, 76, 59, 16, 44, 86, 44, 218, 107, 171, 113, 193, 37, 198, 216, 229, 30, 228, 216, 249, 248, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}