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: 336047d4eda82b8d6b095ac1741302d2eeb2f165edd8a36512a7d540d4f6f733
Tx prefix hash: f05f3fb7fccf99b1a7cd449ff3d3ea9496f66bf08511096d2dd8b4de9e2a8679
Tx public key: 8e3f5b955a915a19789e6cf5c19b886825eb6d0e6781916f0097c4fd95bebec8
| Timestamp: 1779457122 | Timestamp [UTC]: 2026-05-22 13:38:42 | Age [y:d:h:m:s]: 00:017:13:01:54 |
| Block: 398 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7498 | RingCT/type: yes/0 |
| Extra: 018e3f5b955a915a19789e6cf5c19b886825eb6d0e6781916f0097c4fd95bebec802090000000593369e7d00 | ||
1 output(s) for total of 35.157739928979 HMNY
| stealth address | amount | amount idx | tag |
| 00: ceffc6e714514430f8ffa4c8af0955920acff218cff0b2ec490668cebdac60f3 | 35.157739928979 | 398 of 0 | <ba> |
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": 458,
"vin": [ {
"gen": {
"height": 398
}
}
],
"vout": [ {
"amount": 35157739928979,
"target": {
"tagged_key": {
"key": "ceffc6e714514430f8ffa4c8af0955920acff218cff0b2ec490668cebdac60f3",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 142, 63, 91, 149, 90, 145, 90, 25, 120, 158, 108, 245, 193, 155, 136, 104, 37, 235, 109, 14, 103, 129, 145, 111, 0, 151, 196, 253, 149, 190, 190, 200, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}