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: 6861d6ca8646c74c6d8edd7abffa35c974532aa64e7b65bfa5d20239e4218ccc
Tx prefix hash: a19f33bde196861343e48c04f672bbae9606956aeb4eabd75449985ca62c4b9c
Tx public key: e18b0ec68241ed141c2605c03442059fe1b40f8865999b1ab28db8c4f70f3686
| Timestamp: 1779935514 | Timestamp [UTC]: 2026-05-28 02:31:54 | Age [y:d:h:m:s]: 00:016:08:30:22 |
| Block: 3433 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5312 | RingCT/type: yes/0 |
| Extra: 01e18b0ec68241ed141c2605c03442059fe1b40f8865999b1ab28db8c4f70f368602090000000126697be300 | ||
1 output(s) for total of 34.954806439239 HMNY
| stealth address | amount | amount idx | tag |
| 00: 200a15c18fae4cc4a3d26904e5330a50ad3c4f6f5b6bd5937a8a1c704a942434 | 34.954806439239 | 4150 of 0 | <1a> |
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": 3493,
"vin": [ {
"gen": {
"height": 3433
}
}
],
"vout": [ {
"amount": 34954806439239,
"target": {
"tagged_key": {
"key": "200a15c18fae4cc4a3d26904e5330a50ad3c4f6f5b6bd5937a8a1c704a942434",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 225, 139, 14, 198, 130, 65, 237, 20, 28, 38, 5, 192, 52, 66, 5, 159, 225, 180, 15, 136, 101, 153, 155, 26, 178, 141, 184, 196, 247, 15, 54, 134, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}