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: e30060a6924d0128494db61b406ad730ae1892cca23d60ffcb6b6657a566fc91
Tx prefix hash: 501fe042d9efd6f1eae75b7d2a55fb28b54e59c0af07ed5122e0b40744f6b65c
Tx public key: ee2b3ab7a254640020e339ac5088816c452b1adcbe36db41b3db4fc72fd9890f
| Timestamp: 1780835320 | Timestamp [UTC]: 2026-06-07 12:28:40 | Age [y:d:h:m:s]: 00:001:12:18:07 |
| Block: 7397 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 489 | RingCT/type: yes/0 |
| Extra: 01ee2b3ab7a254640020e339ac5088816c452b1adcbe36db41b3db4fc72fd9890f020900000001e49593ff00 | ||
1 output(s) for total of 34.691518912319 HMNY
| stealth address | amount | amount idx | tag |
| 00: a9e67d86e63f37a90b9a8d372ee5e1665563d71f5a7e5821468d66ee5de21cf4 | 34.691518912319 | 9107 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": 7457,
"vin": [ {
"gen": {
"height": 7397
}
}
],
"vout": [ {
"amount": 34691518912319,
"target": {
"tagged_key": {
"key": "a9e67d86e63f37a90b9a8d372ee5e1665563d71f5a7e5821468d66ee5de21cf4",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 238, 43, 58, 183, 162, 84, 100, 0, 32, 227, 57, 172, 80, 136, 129, 108, 69, 43, 26, 220, 190, 54, 219, 65, 179, 219, 79, 199, 47, 217, 137, 15, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}