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: b69d07123b17eeaba1d27490e4031adb15ddbf3773a5477063d78a53440206d4
Tx prefix hash: 2269bf00d7e5ee1dc0efc5335bd40b080e95e1b58bbeab7dae4c9293f7e10499
Tx public key: 9c7648e7345418981ca22595865cb76c7be585baba4abf587ecd9c15d3a284e5
| Timestamp: 1780691423 | Timestamp [UTC]: 2026-06-05 20:30:23 | Age [y:d:h:m:s]: 00:003:06:19:25 |
| Block: 5726 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2194 | RingCT/type: yes/0 |
| Extra: 019c7648e7345418981ca22595865cb76c7be585baba4abf587ecd9c15d3a284e5020900000001e49593ff00 | ||
1 output(s) for total of 34.802263505811 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ad6689bb9d02578ce63d2ab671560e49580049ca9aeca25ff07c67201a6bf7e | 34.802263505811 | 7179 of 0 | <69> |
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": 5786,
"vin": [ {
"gen": {
"height": 5726
}
}
],
"vout": [ {
"amount": 34802263505811,
"target": {
"tagged_key": {
"key": "3ad6689bb9d02578ce63d2ab671560e49580049ca9aeca25ff07c67201a6bf7e",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 156, 118, 72, 231, 52, 84, 24, 152, 28, 162, 37, 149, 134, 92, 183, 108, 123, 229, 133, 186, 186, 74, 191, 88, 126, 205, 156, 21, 211, 162, 132, 229, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}