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: 3e2dbfd2a4beb4be3a1b58805cb2e82b9d1d68f386a037536ff0d35011929184
Tx prefix hash: a0b18919bc966c7e77207b0f6b3ab6ffd3f99fcfffce8d93be3f9fc9bea6ef3c
Tx public key: 342d4ac2d037544fa69fdebad1f885439c76ea3eb4567c48e1c26cfb4cf0a5e6
| Timestamp: 1779642123 | Timestamp [UTC]: 2026-05-24 17:02:03 | Age [y:d:h:m:s]: 00:015:09:38:33 |
| Block: 1376 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6520 | RingCT/type: yes/0 |
| Extra: 01342d4ac2d037544fa69fdebad1f885439c76ea3eb4567c48e1c26cfb4cf0a5e6020900000001ba6d17be00 | ||
1 output(s) for total of 35.092218207466 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0d7be83781b87dd9526a6253697976db7fd04958551df0f58d68cf84e1e3ce7 | 35.092218207466 | 1526 of 0 | <7b> |
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": 1436,
"vin": [ {
"gen": {
"height": 1376
}
}
],
"vout": [ {
"amount": 35092218207466,
"target": {
"tagged_key": {
"key": "a0d7be83781b87dd9526a6253697976db7fd04958551df0f58d68cf84e1e3ce7",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 52, 45, 74, 194, 208, 55, 84, 79, 166, 159, 222, 186, 209, 248, 133, 67, 156, 118, 234, 62, 180, 86, 124, 72, 225, 194, 108, 251, 76, 240, 165, 230, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}