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: a3a002738f34469ad1c9babf7e5a89e5fda8f8aec56094eaa1e39961646736f4
Tx prefix hash: c9d4041f03cb091788f37481db50a624f3eef517146aaa66ce8404d0f1094c19
Tx public key: 69c52f6eda0f3ad804499fbd0dfae663109c95a708692f2768b0012cfae5e9db
| Timestamp: 1780689767 | Timestamp [UTC]: 2026-06-05 20:02:47 | Age [y:d:h:m:s]: 00:003:05:33:10 |
| Block: 5619 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2267 | RingCT/type: yes/0 |
| Extra: 0169c52f6eda0f3ad804499fbd0dfae663109c95a708692f2768b0012cfae5e9db020900000001e49593ff00 | ||
1 output(s) for total of 34.809366902733 HMNY
| stealth address | amount | amount idx | tag |
| 00: 60c934a7aa130dd033648b47ec72b4d1cea86e98b9c74d82b176f6c5a1de6f4b | 34.809366902733 | 7066 of 0 | <20> |
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": 5679,
"vin": [ {
"gen": {
"height": 5619
}
}
],
"vout": [ {
"amount": 34809366902733,
"target": {
"tagged_key": {
"key": "60c934a7aa130dd033648b47ec72b4d1cea86e98b9c74d82b176f6c5a1de6f4b",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 105, 197, 47, 110, 218, 15, 58, 216, 4, 73, 159, 189, 13, 250, 230, 99, 16, 156, 149, 167, 8, 105, 47, 39, 104, 176, 1, 44, 250, 229, 233, 219, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}