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: f90f0aebdb8fefef2b3095fc558884a6cdba6b1f0cf16a542a766e52ba152ea7
Tx prefix hash: e5738d8d5dfe2cefdf626d73f12e6de232e90abbfc167a24ea44de32d1aa0cd9
Tx public key: 5d65026db0b850b67e91cf091b718b674d9aee59a397525aef17e6c7b892e1bd
| Timestamp: 1779784584 | Timestamp [UTC]: 2026-05-26 08:36:24 | Age [y:d:h:m:s]: 00:014:08:32:39 |
| Block: 2147 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6587 | RingCT/type: yes/0 |
| Extra: 015d65026db0b850b67e91cf091b718b674d9aee59a397525aef17e6c7b892e1bd02090000000126697be300 | ||
1 output(s) for total of 35.040650668512 HMNY
| stealth address | amount | amount idx | tag |
| 00: 823467852c1bc8cb15411286cfb252658d2028480b49a1063c1be523d13d0f89 | 35.040650668512 | 2477 of 0 | <c4> |
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": 2207,
"vin": [ {
"gen": {
"height": 2147
}
}
],
"vout": [ {
"amount": 35040650668512,
"target": {
"tagged_key": {
"key": "823467852c1bc8cb15411286cfb252658d2028480b49a1063c1be523d13d0f89",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 93, 101, 2, 109, 176, 184, 80, 182, 126, 145, 207, 9, 27, 113, 139, 103, 77, 154, 238, 89, 163, 151, 82, 90, 239, 23, 230, 199, 184, 146, 225, 189, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}