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: 166a8aa56a53e87703ec1d101a6f05cce949846541ebc668d162202022148c2c
Tx prefix hash: af55f31544673681725942730474ab3233b7f15a1c162a8939587578ea48ac1e
Tx public key: fc2e6fe069008f3e02eca11b0057c5d1a950d9d0f9bc0da266f98fd8534618b1
| Timestamp: 1779872069 | Timestamp [UTC]: 2026-05-27 08:54:29 | Age [y:d:h:m:s]: 00:012:15:52:18 |
| Block: 2827 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5059 | RingCT/type: yes/0 |
| Extra: 01fc2e6fe069008f3e02eca11b0057c5d1a950d9d0f9bc0da266f98fd8534618b102090000000126697be300 | ||
1 output(s) for total of 34.995232463945 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f1276f6ee93ed1945f29384ee1ab304bc1dd98fb4f160d594ddf1d8d7c16157 | 34.995232463945 | 3345 of 0 | <b9> |
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": 2887,
"vin": [ {
"gen": {
"height": 2827
}
}
],
"vout": [ {
"amount": 34995232463945,
"target": {
"tagged_key": {
"key": "8f1276f6ee93ed1945f29384ee1ab304bc1dd98fb4f160d594ddf1d8d7c16157",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 252, 46, 111, 224, 105, 0, 143, 62, 2, 236, 161, 27, 0, 87, 197, 209, 169, 80, 217, 208, 249, 188, 13, 162, 102, 249, 143, 216, 83, 70, 24, 177, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}