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: d29d845a60517bd3179cbd3fa62b833fcb9624f3cf54625f3468b1f1099ec91b
Tx prefix hash: 693a7e50e55ba498db83e7fb5608642fef536ecfe8b99e562ad11e0356ccb51a
Tx public key: e7bd79efe4c17371abb4766bd02b30fb1a18e98ddf86b1c624bb6dcda9c763ac
| Timestamp: 1780893460 | Timestamp [UTC]: 2026-06-08 04:37:40 | Age [y:d:h:m:s]: 00:000:20:58:17 |
| Block: 7748 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 138 | RingCT/type: yes/0 |
| Extra: 01e7bd79efe4c17371abb4766bd02b30fb1a18e98ddf86b1c624bb6dcda9c763ac0209000000014a728a4c00 | ||
1 output(s) for total of 34.668301406635 HMNY
| stealth address | amount | amount idx | tag |
| 00: a4893578246d6d986eb9f81c1ba4eecd5a19f8d5b007fbc581a7880d08dd16e0 | 34.668301406635 | 9592 of 0 | <25> |
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": 7808,
"vin": [ {
"gen": {
"height": 7748
}
}
],
"vout": [ {
"amount": 34668301406635,
"target": {
"tagged_key": {
"key": "a4893578246d6d986eb9f81c1ba4eecd5a19f8d5b007fbc581a7880d08dd16e0",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 231, 189, 121, 239, 228, 193, 115, 113, 171, 180, 118, 107, 208, 43, 48, 251, 26, 24, 233, 141, 223, 134, 177, 198, 36, 187, 109, 205, 169, 199, 99, 172, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}