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: 459daada4c1f8216f0cfb4eef426dfd5a334545878da83eaae83a011bbd90f33
Tx prefix hash: c24cacf476c431ea5f82b3d304aebb3a71e20a7e1dbf998ae2b8e8a66f2488d4
Tx public key: a436cd46d0ac47f0319e07fb21b78a84cc682842d1a21707d877b0a689abd164
| Timestamp: 1780110234 | Timestamp [UTC]: 2026-05-30 03:03:54 | Age [y:d:h:m:s]: 00:014:08:17:11 |
| Block: 4852 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3893 | RingCT/type: yes/0 |
| Extra: 01a436cd46d0ac47f0319e07fb21b78a84cc682842d1a21707d877b0a689abd16402090000000326697be300 | ||
1 output(s) for total of 34.860328108697 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0e383ae5c93fac120184762fc2c89b8cd05e2bb91de36e40f5f7f6a30399725 | 34.860328108697 | 6124 of 0 | <db> |
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": 4912,
"vin": [ {
"gen": {
"height": 4852
}
}
],
"vout": [ {
"amount": 34860328108697,
"target": {
"tagged_key": {
"key": "e0e383ae5c93fac120184762fc2c89b8cd05e2bb91de36e40f5f7f6a30399725",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 164, 54, 205, 70, 208, 172, 71, 240, 49, 158, 7, 251, 33, 183, 138, 132, 204, 104, 40, 66, 209, 162, 23, 7, 216, 119, 176, 166, 137, 171, 209, 100, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}