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: 21baef7ecdb97e2d4bd863c959802cd0ed0d9e50e35635c329704ef5e37ec3e0
Tx prefix hash: 1c05dd2c6e8bc8fa4eb7868254106269b67f19cf835f2fe67fdd91e18147d0a6
Tx public key: f4b114a38db1a01888d77b1900a6cbb93933031401e7faebc2fda1be0a4a0b8c
| Timestamp: 1779633648 | Timestamp [UTC]: 2026-05-24 14:40:48 | Age [y:d:h:m:s]: 00:023:17:24:33 |
| Block: 999 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7746 | RingCT/type: yes/0 |
| Extra: 01f4b114a38db1a01888d77b1900a6cbb93933031401e7faebc2fda1be0a4a0b8c020900000001ba6d17be00 | ||
1 output(s) for total of 35.117461082751 HMNY
| stealth address | amount | amount idx | tag |
| 00: c330e3fb58b2789e963a8fbc08b5d31b289b2e160ec11d3e0253aff7f8147914 | 35.117461082751 | 1135 of 0 | <91> |
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": 1059,
"vin": [ {
"gen": {
"height": 999
}
}
],
"vout": [ {
"amount": 35117461082751,
"target": {
"tagged_key": {
"key": "c330e3fb58b2789e963a8fbc08b5d31b289b2e160ec11d3e0253aff7f8147914",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 244, 177, 20, 163, 141, 177, 160, 24, 136, 215, 123, 25, 0, 166, 203, 185, 57, 51, 3, 20, 1, 231, 250, 235, 194, 253, 161, 190, 10, 74, 11, 140, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}