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: 03c3f0015c715634d74f09927905277f545cf24bf9a195f7a812b36cb297a254
Tx prefix hash: 884eaa2a94d66cabda854710ba8c608437b45205698ed2180b2cfbc8d61d9822
Tx public key: 8c8e8dd168bc36374e4bc96b64ee6d1c90b7eceba02888c439b47a62b97b76d9
| Timestamp: 1780835909 | Timestamp [UTC]: 2026-06-07 12:38:29 | Age [y:d:h:m:s]: 00:001:10:40:24 |
| Block: 7405 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 481 | RingCT/type: yes/0 |
| Extra: 018c8e8dd168bc36374e4bc96b64ee6d1c90b7eceba02888c439b47a62b97b76d9020900000001e49593ff00 | ||
1 output(s) for total of 34.690989565284 HMNY
| stealth address | amount | amount idx | tag |
| 00: e8b54d2062a11efb9b33125a060132c7053640d2a6f84063fd677a62abf833d4 | 34.690989565284 | 9117 of 0 | <0e> |
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": 7465,
"vin": [ {
"gen": {
"height": 7405
}
}
],
"vout": [ {
"amount": 34690989565284,
"target": {
"tagged_key": {
"key": "e8b54d2062a11efb9b33125a060132c7053640d2a6f84063fd677a62abf833d4",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 140, 142, 141, 209, 104, 188, 54, 55, 78, 75, 201, 107, 100, 238, 109, 28, 144, 183, 236, 235, 160, 40, 136, 196, 57, 180, 122, 98, 185, 123, 118, 217, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}