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: 6704f37ebd4203b77ce989797f511e0a85c7b4bb575292ae796fc2cda64386ba
Tx prefix hash: 58cfcccd54cc5ebeca1c8522fe61d2ca6cdd859b2592c9276fd44a428d5d2540
Tx public key: 65a6747291290ca1ccf66ceffa9459905e8614621efc0e3b34a0d260a78c3835
| Timestamp: 1779989823 | Timestamp [UTC]: 2026-05-28 17:37:03 | Age [y:d:h:m:s]: 00:015:17:25:13 |
| Block: 3985 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4760 | RingCT/type: yes/0 |
| Extra: 0165a6747291290ca1ccf66ceffa9459905e8614621efc0e3b34a0d260a78c383502090000000226697be300 | ||
1 output(s) for total of 34.918023377945 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8abd943b8d5f68b10a341a71d6a71b52109599de35072f6d1f7e1f1ab4cef5a | 34.918023377945 | 4919 of 0 | <00> |
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": 4045,
"vin": [ {
"gen": {
"height": 3985
}
}
],
"vout": [ {
"amount": 34918023377945,
"target": {
"tagged_key": {
"key": "d8abd943b8d5f68b10a341a71d6a71b52109599de35072f6d1f7e1f1ab4cef5a",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 101, 166, 116, 114, 145, 41, 12, 161, 204, 246, 108, 239, 250, 148, 89, 144, 94, 134, 20, 98, 30, 252, 14, 59, 52, 160, 210, 96, 167, 140, 56, 53, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}