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: 2684f496dd1e70a1e4c193d20eaced445b7bafa97f753b223e6e361c10a8f566
Tx prefix hash: d2478673838e82ba2ddd8636df0d94b38e372dabd43ef34bfd6c6e2dd526fea2
Tx public key: 078a2b16cc4d9520d2a6c5bef5adcf6f311766cf8e3fbf5bd2c6bd02421cc813
| Timestamp: 1780039206 | Timestamp [UTC]: 2026-05-29 07:20:06 | Age [y:d:h:m:s]: 00:010:19:29:42 |
| Block: 4266 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3654 | RingCT/type: yes/0 |
| Extra: 01078a2b16cc4d9520d2a6c5bef5adcf6f311766cf8e3fbf5bd2c6bd02421cc81302090000000a26697be300 | ||
1 output(s) for total of 34.899313537253 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb6ff3072e5f89ca8ba5ce132edc2fbb36af914985ff3f7a8c85ee3660330098 | 34.899313537253 | 5329 of 0 | <6c> |
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": 4326,
"vin": [ {
"gen": {
"height": 4266
}
}
],
"vout": [ {
"amount": 34899313537253,
"target": {
"tagged_key": {
"key": "eb6ff3072e5f89ca8ba5ce132edc2fbb36af914985ff3f7a8c85ee3660330098",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 7, 138, 43, 22, 204, 77, 149, 32, 210, 166, 197, 190, 245, 173, 207, 111, 49, 23, 102, 207, 142, 63, 191, 91, 210, 198, 189, 2, 66, 28, 200, 19, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}