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: b63b1ad3020c6a7e857abbed8ea12a0e80b3dca9d956b685e0944642e6cca8dd
Tx prefix hash: 955095ff5e34e9d244b3e69c2cc689b6e3d11da4ead7a0bbd35c410164c94162
Tx public key: 526e442ac848f5baa6e50d49a2dcf93fba71d1c4e88785c4d67cb73474574a4e
| Timestamp: 1779989986 | Timestamp [UTC]: 2026-05-28 17:39:46 | Age [y:d:h:m:s]: 00:011:05:39:07 |
| Block: 3987 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3899 | RingCT/type: yes/0 |
| Extra: 01526e442ac848f5baa6e50d49a2dcf93fba71d1c4e88785c4d67cb73474574a4e02090000000226697be300 | ||
1 output(s) for total of 34.920512176384 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d4cd78d8e81ac0668175eceb10f9094c1fccf010403b11257df50b3a9995360 | 34.920512176384 | 4921 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": 4047,
"vin": [ {
"gen": {
"height": 3987
}
}
],
"vout": [ {
"amount": 34920512176384,
"target": {
"tagged_key": {
"key": "3d4cd78d8e81ac0668175eceb10f9094c1fccf010403b11257df50b3a9995360",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 82, 110, 68, 42, 200, 72, 245, 186, 166, 229, 13, 73, 162, 220, 249, 63, 186, 113, 209, 196, 232, 135, 133, 196, 214, 124, 183, 52, 116, 87, 74, 78, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}