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: 509df55d68757b473feec336df670615eb93b23cffa38500e232eeefa89a8007
Tx prefix hash: 33053f0cb5a312045130ca92a27d4ef293b17bece336c7e0756c075292cca425
Tx public key: d74795f7a61e46f86140bcb5a6dfeea26f75704ecfdca28aa29084d83aa93dcf
| Timestamp: 1780706961 | Timestamp [UTC]: 2026-06-06 00:49:21 | Age [y:d:h:m:s]: 00:002:23:57:26 |
| Block: 6121 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1765 | RingCT/type: yes/0 |
| Extra: 01d74795f7a61e46f86140bcb5a6dfeea26f75704ecfdca28aa29084d83aa93dcf020900000001e49593ff00 | ||
1 output(s) for total of 34.776053235861 HMNY
| stealth address | amount | amount idx | tag |
| 00: bce475687363f5e97ced4fa8e746a713499ea4421b6eda0e8c28ed63d3bf7c68 | 34.776053235861 | 7594 of 0 | <37> |
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": 6181,
"vin": [ {
"gen": {
"height": 6121
}
}
],
"vout": [ {
"amount": 34776053235861,
"target": {
"tagged_key": {
"key": "bce475687363f5e97ced4fa8e746a713499ea4421b6eda0e8c28ed63d3bf7c68",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 215, 71, 149, 247, 166, 30, 70, 248, 97, 64, 188, 181, 166, 223, 238, 162, 111, 117, 112, 78, 207, 220, 162, 138, 162, 144, 132, 216, 58, 169, 61, 207, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}