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: 62853c8207b82a870cf8a58bfbeeaa7d4349961b295ee5ea428825863c2b5de5
Tx prefix hash: 68c45bdce6e085146bcb21571b5d632d46ca36ea88d65f74ff0476a925d8a13f
Tx public key: 89bf9fb247374d7ce3a4a69155624e1961a1e324b1ce3e4c6583ce04e16069d0
| Timestamp: 1779972027 | Timestamp [UTC]: 2026-05-28 12:40:27 | Age [y:d:h:m:s]: 00:015:22:21:49 |
| Block: 3854 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4891 | RingCT/type: yes/0 |
| Extra: 0189bf9fb247374d7ce3a4a69155624e1961a1e324b1ce3e4c6583ce04e16069d002090000000626697be300 | ||
1 output(s) for total of 34.930869986932 HMNY
| stealth address | amount | amount idx | tag |
| 00: 768eae4a0122238638f970dbd0ecc8c4b9f66a3a6d32273af8cb7a22f870fd68 | 34.930869986932 | 4706 of 0 | <da> |
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": 3914,
"vin": [ {
"gen": {
"height": 3854
}
}
],
"vout": [ {
"amount": 34930869986932,
"target": {
"tagged_key": {
"key": "768eae4a0122238638f970dbd0ecc8c4b9f66a3a6d32273af8cb7a22f870fd68",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 137, 191, 159, 178, 71, 55, 77, 124, 227, 164, 166, 145, 85, 98, 78, 25, 97, 161, 227, 36, 177, 206, 62, 76, 101, 131, 206, 4, 225, 96, 105, 208, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}