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: 3ca16424f35d8e9dff832e24d032f9553aa0d5899611c53a602efe35c5304511
Tx prefix hash: c0f3f88200b80c89ae1dbbfc9333d005df9090aa62d1ee8bf161200628d8feb5
Tx public key: 390ae39c0c5cfb2e0f91d7158cf79cc4446ee24d30d9137ce2ceec4cfa363f1d
| Timestamp: 1779459422 | Timestamp [UTC]: 2026-05-22 14:17:02 | Age [y:d:h:m:s]: 00:017:11:18:55 |
| Block: 423 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7463 | RingCT/type: yes/0 |
| Extra: 01390ae39c0c5cfb2e0f91d7158cf79cc4446ee24d30d9137ce2ceec4cfa363f1d02090000000293369e7d00 | ||
1 output(s) for total of 35.156063515670 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8352a1702e3229018a1f05e62e7fe85df676568a41f894f75b721c269728df7a | 35.156063515670 | 427 of 0 | <c7> |
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": 483,
"vin": [ {
"gen": {
"height": 423
}
}
],
"vout": [ {
"amount": 35156063515670,
"target": {
"tagged_key": {
"key": "8352a1702e3229018a1f05e62e7fe85df676568a41f894f75b721c269728df7a",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 57, 10, 227, 156, 12, 92, 251, 46, 15, 145, 215, 21, 140, 247, 156, 196, 68, 110, 226, 77, 48, 217, 19, 124, 226, 206, 236, 76, 250, 54, 63, 29, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}