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: c6f4946cf22fa5146e7193ee9a0d6d4dced427dc868e37c588857d0f0534bd13
Tx prefix hash: 5f0fe158817fe241086c3696b5ca41f0119fe1766b1319dd357e496055b9f0c3
Tx public key: 3cae4f104eacf6fcf568f5080af4f348a9ab5331b10952acc0d0585f6852c161
| Timestamp: 1779874553 | Timestamp [UTC]: 2026-05-27 09:35:53 | Age [y:d:h:m:s]: 00:012:18:02:57 |
| Block: 2863 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5079 | RingCT/type: yes/0 |
| Extra: 013cae4f104eacf6fcf568f5080af4f348a9ab5331b10952acc0d0585f6852c16102090000000126697be300 | ||
1 output(s) for total of 34.992829612233 HMNY
| stealth address | amount | amount idx | tag |
| 00: a801e0156745f1dd96e6c5fd65f71f3a85cdeb5de8a5239a42d3fafdf0830bbd | 34.992829612233 | 3389 of 0 | <85> |
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": 2923,
"vin": [ {
"gen": {
"height": 2863
}
}
],
"vout": [ {
"amount": 34992829612233,
"target": {
"tagged_key": {
"key": "a801e0156745f1dd96e6c5fd65f71f3a85cdeb5de8a5239a42d3fafdf0830bbd",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 60, 174, 79, 16, 78, 172, 246, 252, 245, 104, 245, 8, 10, 244, 243, 72, 169, 171, 83, 49, 177, 9, 82, 172, 192, 208, 88, 95, 104, 82, 193, 97, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}