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: 3321123c832f7e1ae55a7e3d62c8fd190247ce357183b7a41703ae24323b937f
Tx prefix hash: 0ff30af09fe5415216aacacc74df8693f365d28ac6e1934790c54f1690e8abfe
Tx public key: bd04f20058fd1ec5d1fc2993dc7f584f1bd8ac6a721b65df6474aebd84da381f
| Timestamp: 1779718405 | Timestamp [UTC]: 2026-05-25 14:13:25 | Age [y:d:h:m:s]: 00:014:10:33:22 |
| Block: 1701 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6185 | RingCT/type: yes/0 |
| Extra: 01bd04f20058fd1ec5d1fc2993dc7f584f1bd8ac6a721b65df6474aebd84da381f020900000002ba6d17be00 | ||
1 output(s) for total of 35.070471671948 HMNY
| stealth address | amount | amount idx | tag |
| 00: a4952f30e7c0ac9a274c7541e6aaefa049f6807fab729fcfe9c9cd12ff988600 | 35.070471671948 | 1872 of 0 | <2b> |
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": 1761,
"vin": [ {
"gen": {
"height": 1701
}
}
],
"vout": [ {
"amount": 35070471671948,
"target": {
"tagged_key": {
"key": "a4952f30e7c0ac9a274c7541e6aaefa049f6807fab729fcfe9c9cd12ff988600",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 189, 4, 242, 0, 88, 253, 30, 197, 209, 252, 41, 147, 220, 127, 88, 79, 27, 216, 172, 106, 114, 27, 101, 223, 100, 116, 174, 189, 132, 218, 56, 31, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}