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: 7279d5defc7c7dfdd2903dd2ad651b32223651d091ca8e742b275bb221d6950c
Tx prefix hash: bc9d731ac217ca72e958c28401196d3c05582fae597c3e24e0a8d5b253951d6c
Tx public key: 81f449e0ae5b34b138f0f2c2e6c37b00989fa892a17681191bc6c5ba601f7bb5
| Timestamp: 1780839772 | Timestamp [UTC]: 2026-06-07 13:42:52 | Age [y:d:h:m:s]: 00:001:11:53:05 |
| Block: 7452 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 434 | RingCT/type: yes/0 |
| Extra: 0181f449e0ae5b34b138f0f2c2e6c37b00989fa892a17681191bc6c5ba601f7bb5020900000002e49593ff00 | ||
1 output(s) for total of 34.687879814566 HMNY
| stealth address | amount | amount idx | tag |
| 00: e5bc47e0f3ea7024d43bd03e289418e738692fb3d21a94431bdda2fe4d34afc8 | 34.687879814566 | 9178 of 0 | <b8> |
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": 7512,
"vin": [ {
"gen": {
"height": 7452
}
}
],
"vout": [ {
"amount": 34687879814566,
"target": {
"tagged_key": {
"key": "e5bc47e0f3ea7024d43bd03e289418e738692fb3d21a94431bdda2fe4d34afc8",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 129, 244, 73, 224, 174, 91, 52, 177, 56, 240, 242, 194, 230, 195, 123, 0, 152, 159, 168, 146, 161, 118, 129, 25, 27, 198, 197, 186, 96, 31, 123, 181, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}