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: a7cbaa655b6e57585b967544834c6d45d15e4b7feabd5621eed678fa01efd010
Tx prefix hash: 316614c179dd3cf42e6f745eb7540d4144fabb1c7db6f369c1bc3aba7cfb351a
Tx public key: 92c2feda3440df175457e8f78e4701c8b5252cc6da06c704c85810b7fb4c2283
| Timestamp: 1780863150 | Timestamp [UTC]: 2026-06-07 20:12:30 | Age [y:d:h:m:s]: 00:001:03:06:23 |
| Block: 7637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 249 | RingCT/type: yes/0 |
| Extra: 0192c2feda3440df175457e8f78e4701c8b5252cc6da06c704c85810b7fb4c2283020900000001e49593ff00 | ||
1 output(s) for total of 34.675642014308 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a3659765a33be41828d18c6a4116a6b6ab8fae3679af7e46810703fef0c4680 | 34.675642014308 | 9441 of 0 | <6f> |
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": 7697,
"vin": [ {
"gen": {
"height": 7637
}
}
],
"vout": [ {
"amount": 34675642014308,
"target": {
"tagged_key": {
"key": "7a3659765a33be41828d18c6a4116a6b6ab8fae3679af7e46810703fef0c4680",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 146, 194, 254, 218, 52, 64, 223, 23, 84, 87, 232, 247, 142, 71, 1, 200, 181, 37, 44, 198, 218, 6, 199, 4, 200, 88, 16, 183, 251, 76, 34, 131, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}