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: 1c63b5de5dd263925bf6688faee1be908d020dd96a965c2f4f86377be34ab3f5
Tx prefix hash: 3e12ff6ae7474567ea552c1be6bc1b624144eae5a5c5599141b7e165058a2013
Tx public key: a3b732b28f87f8acc73aa5f0f325dc96d2aa1b25aaf5bfaaeff276dc522111f5
| Timestamp: 1779846489 | Timestamp [UTC]: 2026-05-27 01:48:09 | Age [y:d:h:m:s]: 00:012:22:58:38 |
| Block: 2461 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5425 | RingCT/type: yes/0 |
| Extra: 01a3b732b28f87f8acc73aa5f0f325dc96d2aa1b25aaf5bfaaeff276dc522111f502090000000126697be300 | ||
1 output(s) for total of 35.019670824160 HMNY
| stealth address | amount | amount idx | tag |
| 00: e317a2ca5193ffbd486d320df88f0f6847f4ff58d5b1859af5b8601adc3047a5 | 35.019670824160 | 2893 of 0 | <86> |
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": 2521,
"vin": [ {
"gen": {
"height": 2461
}
}
],
"vout": [ {
"amount": 35019670824160,
"target": {
"tagged_key": {
"key": "e317a2ca5193ffbd486d320df88f0f6847f4ff58d5b1859af5b8601adc3047a5",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 163, 183, 50, 178, 143, 135, 248, 172, 199, 58, 165, 240, 243, 37, 220, 150, 210, 170, 27, 37, 170, 245, 191, 170, 239, 242, 118, 220, 82, 33, 17, 245, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}