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: fe7a2f85fa7544c130fe4a26c856aec747b28a2b9dc2b1899c8d66ebd35c9bd2
Tx prefix hash: 97736dd268321ee4a2640305bf585e77a7ddce1787309779739d1fea84b0c736
Tx public key: 028891b47361338a1e8664118c38ab21092b776949569d89dc077583ef911e63
| Timestamp: 1780821186 | Timestamp [UTC]: 2026-06-07 08:33:06 | Age [y:d:h:m:s]: 00:006:02:47:59 |
| Block: 7177 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1568 | RingCT/type: yes/0 |
| Extra: 01028891b47361338a1e8664118c38ab21092b776949569d89dc077583ef911e63020900000002e49593ff00 | ||
1 output(s) for total of 34.706079121501 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9ddeadf8f943ef81314b0f6fe9de37cda98386cc62a5f0534f853aafa395ac84 | 34.706079121501 | 8841 of 0 | <d1> |
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": 7237,
"vin": [ {
"gen": {
"height": 7177
}
}
],
"vout": [ {
"amount": 34706079121501,
"target": {
"tagged_key": {
"key": "9ddeadf8f943ef81314b0f6fe9de37cda98386cc62a5f0534f853aafa395ac84",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 2, 136, 145, 180, 115, 97, 51, 138, 30, 134, 100, 17, 140, 56, 171, 33, 9, 43, 119, 105, 73, 86, 157, 137, 220, 7, 117, 131, 239, 145, 30, 99, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}