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: da480866ccd689e45b1e7d012c3708aa6154e67e22205a88333c5bfeb1a6a267
Tx prefix hash: 3c820eac2f6fca3c6b0c1645cbabfc140e3235a472f3d65a37840252bac3d4b3
Tx public key: 424c814bbc6af5e1347f3168b8d678cbd40756df944cc9ca4815775c98d5a68a
| Timestamp: 1780323254 | Timestamp [UTC]: 2026-06-01 14:14:14 | Age [y:d:h:m:s]: 00:007:12:26:22 |
| Block: 5089 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2808 | RingCT/type: yes/0 |
| Extra: 01424c814bbc6af5e1347f3168b8d678cbd40756df944cc9ca4815775c98d5a68a02090000000b26697be300 | ||
1 output(s) for total of 34.844573335446 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61a14fd81057247983346ef001f7af7db0d531fa4f2750b06e70601a95c9136f | 34.844573335446 | 6464 of 0 | <77> |
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": 5149,
"vin": [ {
"gen": {
"height": 5089
}
}
],
"vout": [ {
"amount": 34844573335446,
"target": {
"tagged_key": {
"key": "61a14fd81057247983346ef001f7af7db0d531fa4f2750b06e70601a95c9136f",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 66, 76, 129, 75, 188, 106, 245, 225, 52, 127, 49, 104, 184, 214, 120, 203, 212, 7, 86, 223, 148, 76, 201, 202, 72, 21, 119, 92, 152, 213, 166, 138, 2, 9, 0, 0, 0, 11, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}