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: bdf075f1c172c7b05b8c885a15e06615c7b78b3c97497f9a5d8a55ac3e8d9118
Tx prefix hash: 6fe25c008816ab6388ec8067559be011e2a4c79b3d3a05e54c3c4699cef750d3
Tx public key: a0acc362feee3b879fd3532b34566236b9cf9033e602e4bfea4b036255b2f182
| Timestamp: 1779901058 | Timestamp [UTC]: 2026-05-27 16:57:38 | Age [y:d:h:m:s]: 00:012:06:21:15 |
| Block: 3143 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4743 | RingCT/type: yes/0 |
| Extra: 01a0acc362feee3b879fd3532b34566236b9cf9033e602e4bfea4b036255b2f18202090000000226697be300 | ||
1 output(s) for total of 34.974146396615 HMNY
| stealth address | amount | amount idx | tag |
| 00: fed5f415befa2e8fdb63ae6efa9721eb9325dbc1026906e3b818bfe6e930c624 | 34.974146396615 | 3757 of 0 | <86> |
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": 3203,
"vin": [ {
"gen": {
"height": 3143
}
}
],
"vout": [ {
"amount": 34974146396615,
"target": {
"tagged_key": {
"key": "fed5f415befa2e8fdb63ae6efa9721eb9325dbc1026906e3b818bfe6e930c624",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 160, 172, 195, 98, 254, 238, 59, 135, 159, 211, 83, 43, 52, 86, 98, 54, 185, 207, 144, 51, 230, 2, 228, 191, 234, 75, 3, 98, 85, 178, 241, 130, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}