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: 13c3d8dcd6f814d63e67e5c39235ea773af9fb09a306927cb89c299a7cd6e52c
Tx prefix hash: 1985ec2c0705367de46a69ad130952d125b7e811bd538348f4590923b227995e
Tx public key: f3fcc0bf4c6714a95b86ab1d2c247ccac38933c479138abf1d590f4536b1c67a
| Timestamp: 1779867869 | Timestamp [UTC]: 2026-05-27 07:44:29 | Age [y:d:h:m:s]: 00:012:20:48:33 |
| Block: 2766 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5261 | RingCT/type: yes/0 |
| Extra: 01f3fcc0bf4c6714a95b86ab1d2c247ccac38933c479138abf1d590f4536b1c67a02090000000226697be300 | ||
1 output(s) for total of 34.999304339338 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3abe87e82451df5a1c344ca0001db8fa45c3b5cf7198f540d6d53ba16c12a302 | 34.999304339338 | 3270 of 0 | <0f> |
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": 2826,
"vin": [ {
"gen": {
"height": 2766
}
}
],
"vout": [ {
"amount": 34999304339338,
"target": {
"tagged_key": {
"key": "3abe87e82451df5a1c344ca0001db8fa45c3b5cf7198f540d6d53ba16c12a302",
"view_tag": "0f"
}
}
}
],
"extra": [ 1, 243, 252, 192, 191, 76, 103, 20, 169, 91, 134, 171, 29, 44, 36, 124, 202, 195, 137, 51, 196, 121, 19, 138, 191, 29, 89, 15, 69, 54, 177, 198, 122, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}