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: 0d897aba783a75810a5921bd13dff6e589ee40e93117fbc5ba529271d2b91391
Tx prefix hash: 3a03dd37066790088b6c9c8a93e996c453517efb175dec768eaefe7fb22c09dc
Tx public key: 2d8fc0c12359c30021b7b7ce8eeba53fec60043e94b12c2ee624a6d3aa607e57
| Timestamp: 1779772652 | Timestamp [UTC]: 2026-05-26 05:17:32 | Age [y:d:h:m:s]: 00:013:22:21:18 |
| Block: 2032 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5917 | RingCT/type: yes/0 |
| Extra: 012d8fc0c12359c30021b7b7ce8eeba53fec60043e94b12c2ee624a6d3aa607e5702090000000126697be300 | ||
1 output(s) for total of 35.048337513620 HMNY
| stealth address | amount | amount idx | tag |
| 00: 21a29b74325c3df4667d162ff8fe4adf869f4459eed92e3286ef913eddc90dd7 | 35.048337513620 | 2322 of 0 | <c1> |
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": 2092,
"vin": [ {
"gen": {
"height": 2032
}
}
],
"vout": [ {
"amount": 35048337513620,
"target": {
"tagged_key": {
"key": "21a29b74325c3df4667d162ff8fe4adf869f4459eed92e3286ef913eddc90dd7",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 45, 143, 192, 193, 35, 89, 195, 0, 33, 183, 183, 206, 142, 235, 165, 63, 236, 96, 4, 62, 148, 177, 44, 46, 230, 36, 166, 211, 170, 96, 126, 87, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}