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: 4f363a270d51dedc2a7b1f30324dac6a52dbd5da9f7272acb39056498c073350
Tx prefix hash: 1879131645590a26751edfea36a9660bd6c88b47034361faf1b20051b42b540e
Tx public key: f4564f3541881fe7f3c405d45ef1387abd1ec42f99e7f14059d66abe1a89c1b4
| Timestamp: 1780396067 | Timestamp [UTC]: 2026-06-02 10:27:47 | Age [y:d:h:m:s]: 00:006:14:19:00 |
| Block: 5250 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2636 | RingCT/type: yes/0 |
| Extra: 01f4564f3541881fe7f3c405d45ef1387abd1ec42f99e7f14059d66abe1a89c1b402090000000226697be300 | ||
1 output(s) for total of 34.833874787360 HMNY
| stealth address | amount | amount idx | tag |
| 00: aae54337c694eefd9d2a1b32f05a97073cb56fced75ea330ef4320a268101369 | 34.833874787360 | 6647 of 0 | <54> |
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": 5310,
"vin": [ {
"gen": {
"height": 5250
}
}
],
"vout": [ {
"amount": 34833874787360,
"target": {
"tagged_key": {
"key": "aae54337c694eefd9d2a1b32f05a97073cb56fced75ea330ef4320a268101369",
"view_tag": "54"
}
}
}
],
"extra": [ 1, 244, 86, 79, 53, 65, 136, 31, 231, 243, 196, 5, 212, 94, 241, 56, 122, 189, 30, 196, 47, 153, 231, 241, 64, 89, 214, 106, 190, 26, 137, 193, 180, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}