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: 51b8bd45ca3db994de015c30d2f47c78a3996f9b3025b31f707dc3eb374e8232
Tx prefix hash: f910168d9fa59e649dfc5318a106ca373d86de65b7abf36fa3dc97c8552e95e6
Tx public key: ade7d7ad1613d31820dc5215857b506ee84f9cc5c6db92e8a85c7de762e6b804
| Timestamp: 1779644302 | Timestamp [UTC]: 2026-05-24 17:38:22 | Age [y:d:h:m:s]: 00:015:07:57:35 |
| Block: 1429 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6457 | RingCT/type: yes/0 |
| Extra: 01ade7d7ad1613d31820dc5215857b506ee84f9cc5c6db92e8a85c7de762e6b804020900000001ba6d17be00 | ||
1 output(s) for total of 35.088670929378 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6f0d79d423e5896db0601e62a3df9d61d31482a32c606ce464061b528f71339 | 35.088670929378 | 1581 of 0 | <5a> |
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": 1489,
"vin": [ {
"gen": {
"height": 1429
}
}
],
"vout": [ {
"amount": 35088670929378,
"target": {
"tagged_key": {
"key": "b6f0d79d423e5896db0601e62a3df9d61d31482a32c606ce464061b528f71339",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 173, 231, 215, 173, 22, 19, 211, 24, 32, 220, 82, 21, 133, 123, 80, 110, 232, 79, 156, 197, 198, 219, 146, 232, 168, 92, 125, 231, 98, 230, 184, 4, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}