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: 0dcb02df7dab6f5e902341b7f2ddee648099cb285e58a8b92913e4f5c657528d
Tx prefix hash: 0709bf6e77f45b59c1b0a58ae9c490dce0ee3db40852c5f88b6b286bac4f6444
Tx public key: 94cd1e6bdec09bef63c2475f81e89c8ef6fd43d41b1802b61233711695387186
| Timestamp: 1779640293 | Timestamp [UTC]: 2026-05-24 16:31:33 | Age [y:d:h:m:s]: 00:016:00:37:30 |
| Block: 1287 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7447 | RingCT/type: yes/0 |
| Extra: 0194cd1e6bdec09bef63c2475f81e89c8ef6fd43d41b1802b61233711695387186020900000002ba6d17be00 | ||
1 output(s) for total of 35.098175764197 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09aa7d1029dc95bc86093b9bebc3637a95d744a27a8fc4c4a3698c422f386eb2 | 35.098175764197 | 1435 of 0 | <fa> |
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": 1347,
"vin": [ {
"gen": {
"height": 1287
}
}
],
"vout": [ {
"amount": 35098175764197,
"target": {
"tagged_key": {
"key": "09aa7d1029dc95bc86093b9bebc3637a95d744a27a8fc4c4a3698c422f386eb2",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 148, 205, 30, 107, 222, 192, 155, 239, 99, 194, 71, 95, 129, 232, 156, 142, 246, 253, 67, 212, 27, 24, 2, 182, 18, 51, 113, 22, 149, 56, 113, 134, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}