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: d9d1ad76324f2e1bc0ea281454008e96f18c4f084eb833544f44185fe1512c78
Tx prefix hash: 6b0caa2a46f3d40b3d891c298e7ca1cc82405e66d6269bd0b3a8c648fe8f5f37
Tx public key: 49c4193a77dd0b89ea4f1c4b8e49b3e29b94350767f01418e27a9b1684bdfbd9
| Timestamp: 1779433772 | Timestamp [UTC]: 2026-05-22 07:09:32 | Age [y:d:h:m:s]: 00:017:21:23:30 |
| Block: 61 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7968 | RingCT/type: yes/0 |
| Extra: 0149c4193a77dd0b89ea4f1c4b8e49b3e29b94350767f01418e27a9b1684bdfbd9020900000001a662ed0300 | ||
1 output(s) for total of 35.180345783657 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33cd3ca92f3c5fcb69a4e05632820938629b4cfd312cda70157dd2947288b7bd | 35.180345783657 | 57 of 0 | <ba> |
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": 121,
"vin": [ {
"gen": {
"height": 61
}
}
],
"vout": [ {
"amount": 35180345783657,
"target": {
"tagged_key": {
"key": "33cd3ca92f3c5fcb69a4e05632820938629b4cfd312cda70157dd2947288b7bd",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 73, 196, 25, 58, 119, 221, 11, 137, 234, 79, 28, 75, 142, 73, 179, 226, 155, 148, 53, 7, 103, 240, 20, 24, 226, 122, 155, 22, 132, 189, 251, 217, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}