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: ed6f075d1e3aa0c27d42fb52fe0a5bd3330c1ace38d0195082c09914407eb924
Tx prefix hash: b22d9df9d7130bc85b7408b5332545354677b3738c0b4fe18c8519e449248e87
Tx public key: fa1a86f78a24a3fcfdc144387d8caa6dcaec7e45c05f855cdb424eedea32a0db
| Timestamp: 1779901646 | Timestamp [UTC]: 2026-05-27 17:07:26 | Age [y:d:h:m:s]: 00:012:10:31:24 |
| Block: 3150 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4800 | RingCT/type: yes/0 |
| Extra: 01fa1a86f78a24a3fcfdc144387d8caa6dcaec7e45c05f855cdb424eedea32a0db02090000000126697be300 | ||
1 output(s) for total of 34.973679444055 HMNY
| stealth address | amount | amount idx | tag |
| 00: e1dc27ab9c85cac5c02605f290bd96dcd162672582cd2d754f1fe8656ddd586f | 34.973679444055 | 3766 of 0 | <f2> |
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": 3210,
"vin": [ {
"gen": {
"height": 3150
}
}
],
"vout": [ {
"amount": 34973679444055,
"target": {
"tagged_key": {
"key": "e1dc27ab9c85cac5c02605f290bd96dcd162672582cd2d754f1fe8656ddd586f",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 250, 26, 134, 247, 138, 36, 163, 252, 253, 193, 68, 56, 125, 140, 170, 109, 202, 236, 126, 69, 192, 95, 133, 92, 219, 66, 78, 237, 234, 50, 160, 219, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}