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: 37b89f21b894ec87d4df560c1ab5a923b0e3cc4aa3f8bd8cd15e5670a7247308
Tx prefix hash: 448f70a4ba7dfc16f04d88dd0227fffb0ac5a9644b92cde95b7f1f02800c866a
Tx public key: 7162e38408caaa263bb5ffbac259f966a4cfc6cea8f2396a785e082e6d8317cc
| Timestamp: 1779891662 | Timestamp [UTC]: 2026-05-27 14:21:02 | Age [y:d:h:m:s]: 00:012:08:57:51 |
| Block: 3066 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4820 | RingCT/type: yes/0 |
| Extra: 017162e38408caaa263bb5ffbac259f966a4cfc6cea8f2396a785e082e6d8317cc02090000000326697be300 | ||
1 output(s) for total of 34.979283286276 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a48b60bc6de53541a5ac303bd9c7c4ec25e66e4103d764b0b790f98d9c67f5c | 34.979283286276 | 3650 of 0 | <ac> |
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": 3126,
"vin": [ {
"gen": {
"height": 3066
}
}
],
"vout": [ {
"amount": 34979283286276,
"target": {
"tagged_key": {
"key": "0a48b60bc6de53541a5ac303bd9c7c4ec25e66e4103d764b0b790f98d9c67f5c",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 113, 98, 227, 132, 8, 202, 170, 38, 59, 181, 255, 186, 194, 89, 249, 102, 164, 207, 198, 206, 168, 242, 57, 106, 120, 94, 8, 46, 109, 131, 23, 204, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}