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: cd666a51ec6784338d2e6002bc76fcac9806ca71ef64774696a56435ec980cb0
Tx prefix hash: 0800063bae005e6ef5feb4dd6957e64457cffe864fc81c7f5ae86c951c72e894
Tx public key: b2df37490ad6c4c6017f630e5848fae9f2ebbb9c64b61d33cb7155d9d0fc74c0
| Timestamp: 1779777226 | Timestamp [UTC]: 2026-05-26 06:33:46 | Age [y:d:h:m:s]: 00:013:21:59:16 |
| Block: 2075 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5951 | RingCT/type: yes/0 |
| Extra: 01b2df37490ad6c4c6017f630e5848fae9f2ebbb9c64b61d33cb7155d9d0fc74c002090000000126697be300 | ||
1 output(s) for total of 35.045463104612 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7a1a39170534fb19d0f128ab05b4923875514f143083405652a6c4dd6948ec3 | 35.045463104612 | 2381 of 0 | <43> |
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": 2135,
"vin": [ {
"gen": {
"height": 2075
}
}
],
"vout": [ {
"amount": 35045463104612,
"target": {
"tagged_key": {
"key": "a7a1a39170534fb19d0f128ab05b4923875514f143083405652a6c4dd6948ec3",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 178, 223, 55, 73, 10, 214, 196, 198, 1, 127, 99, 14, 88, 72, 250, 233, 242, 235, 187, 156, 100, 182, 29, 51, 203, 113, 85, 217, 208, 252, 116, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}