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: b5401bbcff7ebe3a767983f1f760917155301c89e5545a143ca8038ec02ecec4
Tx prefix hash: 867a1dcda9941424c4a54a34a22b4e10b14eee1e49bd504b1290336b74477896
Tx public key: c13d2c31f1cf7de5d9385d86bf326b26f605596a01394dbe8c7587e467b06d32
| Timestamp: 1779840938 | Timestamp [UTC]: 2026-05-27 00:15:38 | Age [y:d:h:m:s]: 00:013:01:20:19 |
| Block: 2393 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5493 | RingCT/type: yes/0 |
| Extra: 01c13d2c31f1cf7de5d9385d86bf326b26f605596a01394dbe8c7587e467b06d3202090000000126697be300 | ||
1 output(s) for total of 35.024213164102 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84ce63801a3017c1eddc70bd5f7ca3051d467305cd71e2fac3709e0e15c3b6e7 | 35.024213164102 | 2807 of 0 | <9f> |
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": 2453,
"vin": [ {
"gen": {
"height": 2393
}
}
],
"vout": [ {
"amount": 35024213164102,
"target": {
"tagged_key": {
"key": "84ce63801a3017c1eddc70bd5f7ca3051d467305cd71e2fac3709e0e15c3b6e7",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 193, 61, 44, 49, 241, 207, 125, 229, 217, 56, 93, 134, 191, 50, 107, 38, 246, 5, 89, 106, 1, 57, 77, 190, 140, 117, 135, 228, 103, 176, 109, 50, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}