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: 7127a0314b19968687d4b769c1972f40d1389c2ffb2c710263393a13009aac56
Tx prefix hash: 49355f7b6130f1325a1280c2ab036bb59b724fb2d4162376c4ef8c9b1384cff0
Tx public key: 06b27bada8a727a3d10e469d05616d1175d6b2bf1c58dcfc4ceb25344e9888fd
| Timestamp: 1779728448 | Timestamp [UTC]: 2026-05-25 17:00:48 | Age [y:d:h:m:s]: 00:014:09:11:14 |
| Block: 1869 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6017 | RingCT/type: yes/0 |
| Extra: 0106b27bada8a727a3d10e469d05616d1175d6b2bf1c58dcfc4ceb25344e9888fd020900000010ba6d17be00 | ||
1 output(s) for total of 35.061845670010 HMNY
| stealth address | amount | amount idx | tag |
| 00: 67e059714ef720bec915db62ade522b6220616605a7c5118e8ebfdac42da449c | 35.061845670010 | 2076 of 0 | <59> |
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": 1929,
"vin": [ {
"gen": {
"height": 1869
}
}
],
"vout": [ {
"amount": 35061845670010,
"target": {
"tagged_key": {
"key": "67e059714ef720bec915db62ade522b6220616605a7c5118e8ebfdac42da449c",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 6, 178, 123, 173, 168, 167, 39, 163, 209, 14, 70, 157, 5, 97, 109, 17, 117, 214, 178, 191, 28, 88, 220, 252, 76, 235, 37, 52, 78, 152, 136, 253, 2, 9, 0, 0, 0, 16, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}