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: b01b2dec897d6bf441b099289c631e96c65ec514082d26552d521a000d74f6ef
Tx prefix hash: 7c5ad51ce7f094d4f311c7ae1f779974345f27d1fba7bb0cbf91aededbde3cb9
Tx public key: 4f40a7f506eaeeffba7f255263222b33f4ff8396470058e674f45cfcfa21e450
| Timestamp: 1779927949 | Timestamp [UTC]: 2026-05-28 00:25:49 | Age [y:d:h:m:s]: 00:011:22:53:04 |
| Block: 3387 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4499 | RingCT/type: yes/0 |
| Extra: 014f40a7f506eaeeffba7f255263222b33f4ff8396470058e674f45cfcfa21e45002090000000226697be300 | ||
1 output(s) for total of 34.957873442813 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2af4f69ca727c921d5fd38f4e573a7a6e3797dfa732c4f60722a3b1d9fde8910 | 34.957873442813 | 4092 of 0 | <d1> |
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": 3447,
"vin": [ {
"gen": {
"height": 3387
}
}
],
"vout": [ {
"amount": 34957873442813,
"target": {
"tagged_key": {
"key": "2af4f69ca727c921d5fd38f4e573a7a6e3797dfa732c4f60722a3b1d9fde8910",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 79, 64, 167, 245, 6, 234, 238, 255, 186, 127, 37, 82, 99, 34, 43, 51, 244, 255, 131, 150, 71, 0, 88, 230, 116, 244, 92, 252, 250, 33, 228, 80, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}