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: 186876f31eda50c57974a725efa52ee82528c8bdbec430152cc17f9ac468cb1d
Tx prefix hash: 35917bf696bc27471fcc3e06873b6f7252ba134d37d5017c92bef9ea3e2e6bc5
Tx public key: 8c472a1bce590ff4e035fc087527f782ce527c2382fc73072cdf09eddd3ff1a2
| Timestamp: 1780701772 | Timestamp [UTC]: 2026-06-05 23:22:52 | Age [y:d:h:m:s]: 00:003:01:23:55 |
| Block: 6064 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1822 | RingCT/type: yes/0 |
| Extra: 018c472a1bce590ff4e035fc087527f782ce527c2382fc73072cdf09eddd3ff1a2020900000001e49593ff00 | ||
1 output(s) for total of 34.779834258280 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f07fd4d71ae5d8dc269773d56852b81ac6cd30e54e9da5123d3ac38f478997c | 34.779834258280 | 7535 of 0 | <18> |
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": 6124,
"vin": [ {
"gen": {
"height": 6064
}
}
],
"vout": [ {
"amount": 34779834258280,
"target": {
"tagged_key": {
"key": "0f07fd4d71ae5d8dc269773d56852b81ac6cd30e54e9da5123d3ac38f478997c",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 140, 71, 42, 27, 206, 89, 15, 244, 224, 53, 252, 8, 117, 39, 247, 130, 206, 82, 124, 35, 130, 252, 115, 7, 44, 223, 9, 237, 221, 63, 241, 162, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}