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: d8e00e2936957dbea2946762a339b0491aae6e6de4d1496d6a54196c1000650f
Tx prefix hash: bd835e341c28b5528ea95eff1691bd0fdb07821f93f6dd198e81709d39465342
Tx public key: a9179ea237c1d241e3772d08545349002b418d6663143cce5339e7269dcf1a47
| Timestamp: 1779922868 | Timestamp [UTC]: 2026-05-27 23:01:08 | Age [y:d:h:m:s]: 00:012:00:17:45 |
| Block: 3361 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4525 | RingCT/type: yes/0 |
| Extra: 01a9179ea237c1d241e3772d08545349002b418d6663143cce5339e7269dcf1a4702090000000426697be300 | ||
1 output(s) for total of 34.963022285608 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36dab67db6cb1b7a8a73610d0e95bddfe7d41ed9e8ecc581a9d36202a1fa868c | 34.963022285608 | 4048 of 0 | <35> |
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": 3421,
"vin": [ {
"gen": {
"height": 3361
}
}
],
"vout": [ {
"amount": 34963022285608,
"target": {
"tagged_key": {
"key": "36dab67db6cb1b7a8a73610d0e95bddfe7d41ed9e8ecc581a9d36202a1fa868c",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 169, 23, 158, 162, 55, 193, 210, 65, 227, 119, 45, 8, 84, 83, 73, 0, 43, 65, 141, 102, 99, 20, 60, 206, 83, 57, 231, 38, 157, 207, 26, 71, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}