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: c804895cc15762974b05a1b258eebb2957c17026a844d5201c08b37f8371fe79
Tx prefix hash: 83bcf4b8a1456156f8e1574341be3c44764d938460548e4829e5b5f10959dfde
Tx public key: 689ba4d258f078ab8300dfc4a69114af89aa59434e692056c11c2298a0d9d558
| Timestamp: 1780721417 | Timestamp [UTC]: 2026-06-06 04:50:17 | Age [y:d:h:m:s]: 00:002:20:45:40 |
| Block: 6249 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1637 | RingCT/type: yes/0 |
| Extra: 01689ba4d258f078ab8300dfc4a69114af89aa59434e692056c11c2298a0d9d558020900000002e49593ff00 | ||
1 output(s) for total of 34.767564016716 HMNY
| stealth address | amount | amount idx | tag |
| 00: b75456fce80c551b97742d95b1b1685707d8df0c3c71ecb3724b2a89ffd82090 | 34.767564016716 | 7730 of 0 | <d3> |
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": 6309,
"vin": [ {
"gen": {
"height": 6249
}
}
],
"vout": [ {
"amount": 34767564016716,
"target": {
"tagged_key": {
"key": "b75456fce80c551b97742d95b1b1685707d8df0c3c71ecb3724b2a89ffd82090",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 104, 155, 164, 210, 88, 240, 120, 171, 131, 0, 223, 196, 166, 145, 20, 175, 137, 170, 89, 67, 78, 105, 32, 86, 193, 28, 34, 152, 160, 217, 213, 88, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}