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: 1dd3725816445c9f6e638ca3ec19ed5292fe754c33a7ed7d327875593cf0301d
Tx prefix hash: fef67abc9075e61ea3c6ebfed873f6bf754949b630266e0b4d04f7ed52bb815b
Tx public key: c8c4cd493018ac69b8b461642274d72cae6f08255e819f1a23d276407fc459a0
| Timestamp: 1779803764 | Timestamp [UTC]: 2026-05-26 13:56:04 | Age [y:d:h:m:s]: 00:013:12:44:32 |
| Block: 2325 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5572 | RingCT/type: yes/0 |
| Extra: 01c8c4cd493018ac69b8b461642274d72cae6f08255e819f1a23d276407fc459a002090000000126697be300 | ||
1 output(s) for total of 35.028756093223 HMNY
| stealth address | amount | amount idx | tag |
| 00: fa236c8237db24c14dfc163c0ac6e9e3bf3e492483364d33d28914e2c975d596 | 35.028756093223 | 2719 of 0 | <e0> |
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": 2385,
"vin": [ {
"gen": {
"height": 2325
}
}
],
"vout": [ {
"amount": 35028756093223,
"target": {
"tagged_key": {
"key": "fa236c8237db24c14dfc163c0ac6e9e3bf3e492483364d33d28914e2c975d596",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 200, 196, 205, 73, 48, 24, 172, 105, 184, 180, 97, 100, 34, 116, 215, 44, 174, 111, 8, 37, 94, 129, 159, 26, 35, 210, 118, 64, 127, 196, 89, 160, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}