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: de249100e4c278e40e254139a9fad1ddb844df7034ac9e94dbccadf131bb05b3
Tx prefix hash: 056d44349c4129b0fe7ee369a1e613628b330fe520d8504a9f5375ca9dabfbdd
Tx public key: f225035de4efd1dfe67b08af0efa60d359b5ee9d81da720ed88eed9ef7a625a2
| Timestamp: 1779435891 | Timestamp [UTC]: 2026-05-22 07:44:51 | Age [y:d:h:m:s]: 00:017:17:51:06 |
| Block: 131 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7755 | RingCT/type: yes/0 |
| Extra: 01f225035de4efd1dfe67b08af0efa60d359b5ee9d81da720ed88eed9ef7a625a2020900000001a662ed0300 | ||
1 output(s) for total of 35.175649009818 HMNY
| stealth address | amount | amount idx | tag |
| 00: c21a7b53c692738cc5c2af4ac1df2e58dcf7285711ee5aa642909dcf3fd41a98 | 35.175649009818 | 127 of 0 | <c6> |
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": 191,
"vin": [ {
"gen": {
"height": 131
}
}
],
"vout": [ {
"amount": 35175649009818,
"target": {
"tagged_key": {
"key": "c21a7b53c692738cc5c2af4ac1df2e58dcf7285711ee5aa642909dcf3fd41a98",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 242, 37, 3, 93, 228, 239, 209, 223, 230, 123, 8, 175, 14, 250, 96, 211, 89, 181, 238, 157, 129, 218, 114, 14, 216, 142, 237, 158, 247, 166, 37, 162, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}