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: 1872b834bedee81e253905ef2c263c777963921902672f12f8fa894ecaa2f6ac
Tx prefix hash: 4808ae0037d5eb47372436b63f07e55a0a5243f3043042a3a53bfc220dff3197
Tx public key: 5d8d640d86097c7f0ada11ee8e2dd8f5c491c74e4a4264038f87fc6d1ca8c2ce
| Timestamp: 1780861534 | Timestamp [UTC]: 2026-06-07 19:45:34 | Age [y:d:h:m:s]: 00:001:05:50:23 |
| Block: 7625 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 261 | RingCT/type: yes/0 |
| Extra: 015d8d640d86097c7f0ada11ee8e2dd8f5c491c74e4a4264038f87fc6d1ca8c2ce020900000002e49593ff00 | ||
1 output(s) for total of 34.676435686609 HMNY
| stealth address | amount | amount idx | tag |
| 00: 23e4ba1c4d35dd37a5e86e3be5e446f358705fe036f68837941f914f2e937646 | 34.676435686609 | 9423 of 0 | <8c> |
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": 7685,
"vin": [ {
"gen": {
"height": 7625
}
}
],
"vout": [ {
"amount": 34676435686609,
"target": {
"tagged_key": {
"key": "23e4ba1c4d35dd37a5e86e3be5e446f358705fe036f68837941f914f2e937646",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 93, 141, 100, 13, 134, 9, 124, 127, 10, 218, 17, 238, 142, 45, 216, 245, 196, 145, 199, 78, 74, 66, 100, 3, 143, 135, 252, 109, 28, 168, 194, 206, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}