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: e81d3a74ceb0b23dc71acd7996190389be472f5f41735c7d95b86737e12c6d9a
Tx prefix hash: 09120551493b1eae270bc6e4c6cd3cd6e5002cf7b907ce5564ef1127edf28edd
Tx public key: aced23fcb6dcf0b0fe133f02622061aa5b54613cdfeb5f2950a1a8dac075080a
| Timestamp: 1779803390 | Timestamp [UTC]: 2026-05-26 13:49:50 | Age [y:d:h:m:s]: 00:013:11:46:07 |
| Block: 2323 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5563 | RingCT/type: yes/0 |
| Extra: 01aced23fcb6dcf0b0fe133f02622061aa5b54613cdfeb5f2950a1a8dac075080a02090000000126697be300 | ||
1 output(s) for total of 35.028889717705 HMNY
| stealth address | amount | amount idx | tag |
| 00: efab2c266059c8cb98ded39cc46769105da200ed1e08e1190b4f2b8c535274b3 | 35.028889717705 | 2717 of 0 | <ad> |
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": 2383,
"vin": [ {
"gen": {
"height": 2323
}
}
],
"vout": [ {
"amount": 35028889717705,
"target": {
"tagged_key": {
"key": "efab2c266059c8cb98ded39cc46769105da200ed1e08e1190b4f2b8c535274b3",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 172, 237, 35, 252, 182, 220, 240, 176, 254, 19, 63, 2, 98, 32, 97, 170, 91, 84, 97, 60, 223, 235, 95, 41, 80, 161, 168, 218, 192, 117, 8, 10, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}