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: 7b8365fda062336ba5862488d82f94177b9b2db1fc95b7eb672659080616af61
Tx prefix hash: 38c4e57896730a53ab99dc4f5676fb90901adad99fa376588a57ba965489546c
Tx public key: eac3cdee74e5a411424f3de914041e4f5c11459a2522a356812639f2f59590e4
| Timestamp: 1779487516 | Timestamp [UTC]: 2026-05-22 22:05:16 | Age [y:d:h:m:s]: 00:017:03:30:41 |
| Block: 666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7220 | RingCT/type: yes/0 |
| Extra: 01eac3cdee74e5a411424f3de914041e4f5c11459a2522a356812639f2f59590e4020900000002ba6d17be00 | ||
1 output(s) for total of 35.139772942317 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd4a3693c37b6ae06e288a2086a50865c2204c9028a83ef7d4662b4a1bb83dc4 | 35.139772942317 | 725 of 0 | <04> |
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": 726,
"vin": [ {
"gen": {
"height": 666
}
}
],
"vout": [ {
"amount": 35139772942317,
"target": {
"tagged_key": {
"key": "fd4a3693c37b6ae06e288a2086a50865c2204c9028a83ef7d4662b4a1bb83dc4",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 234, 195, 205, 238, 116, 229, 164, 17, 66, 79, 61, 233, 20, 4, 30, 79, 92, 17, 69, 154, 37, 34, 163, 86, 129, 38, 57, 242, 245, 149, 144, 228, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}