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: a13415c5ae55d4e99266ee7a8de3b0a287fcdbed994043daab406bf752e58f76
Tx prefix hash: 7ff4f23d0e919e8f43470bde5db491b1d9fb8fef2302c5b72e3538f092dfc0c9
Tx public key: 3e88698e7bd179c33f841831223a5d56a9145b5d273e9fe770822a028ee6ad84
| Timestamp: 1779902825 | Timestamp [UTC]: 2026-05-27 17:27:05 | Age [y:d:h:m:s]: 00:012:08:08:52 |
| Block: 3167 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4719 | RingCT/type: yes/0 |
| Extra: 013e88698e7bd179c33f841831223a5d56a9145b5d273e9fe770822a028ee6ad8402090000000126697be300 | ||
1 output(s) for total of 34.972545442364 HMNY
| stealth address | amount | amount idx | tag |
| 00: baa7ec4eec1ff18d7997f5f3f29d8f74beb05da510723d132f06b7ffed10e72d | 34.972545442364 | 3787 of 0 | <8a> |
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": 3227,
"vin": [ {
"gen": {
"height": 3167
}
}
],
"vout": [ {
"amount": 34972545442364,
"target": {
"tagged_key": {
"key": "baa7ec4eec1ff18d7997f5f3f29d8f74beb05da510723d132f06b7ffed10e72d",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 62, 136, 105, 142, 123, 209, 121, 195, 63, 132, 24, 49, 34, 58, 93, 86, 169, 20, 91, 93, 39, 62, 159, 231, 112, 130, 42, 2, 142, 230, 173, 132, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}