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: 21adf4e4482f525b7bfe3300bd534f3a4986453fba7fcd795175ee6c0704707e
Tx prefix hash: c06298b24284c36b0d2fde1b529b8f3c86fe25fcbf007e228096be74c77e1bed
Tx public key: 613fba904d34dec312e40f4fb7dc791f0bbe9c0f6002049ebe418ede14de6923
| Timestamp: 1780861442 | Timestamp [UTC]: 2026-06-07 19:44:02 | Age [y:d:h:m:s]: 00:001:01:28:05 |
| Block: 7624 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 262 | RingCT/type: yes/0 |
| Extra: 01613fba904d34dec312e40f4fb7dc791f0bbe9c0f6002049ebe418ede14de6923020900000003e49593ff00 | ||
1 output(s) for total of 34.676501826787 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2dc8f2925340afa0142e40907e19b3e364dde28fb68d144fa3ef605858fd9f9f | 34.676501826787 | 9422 of 0 | <88> |
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": 7684,
"vin": [ {
"gen": {
"height": 7624
}
}
],
"vout": [ {
"amount": 34676501826787,
"target": {
"tagged_key": {
"key": "2dc8f2925340afa0142e40907e19b3e364dde28fb68d144fa3ef605858fd9f9f",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 97, 63, 186, 144, 77, 52, 222, 195, 18, 228, 15, 79, 183, 220, 121, 31, 11, 190, 156, 15, 96, 2, 4, 158, 190, 65, 142, 222, 20, 222, 105, 35, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}