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: 0872f55b887922594f19cb5c9a950a689aa81b4766570938f08dabe0952aeb78
Tx prefix hash: 6735039daab4914eacb30b5aa605be5cf9794438a08c7b3addcc72ea9b1111e9
Tx public key: f6c512ce9166fbf100d34bf898c66bc0f3d84e4d7d4ca14ae7bba4cc49fb37c7
| Timestamp: 1780067221 | Timestamp [UTC]: 2026-05-29 15:07:01 | Age [y:d:h:m:s]: 00:010:09:39:46 |
| Block: 4602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3284 | RingCT/type: yes/0 |
| Extra: 01f6c512ce9166fbf100d34bf898c66bc0f3d84e4d7d4ca14ae7bba4cc49fb37c702090000000326697be300 | ||
1 output(s) for total of 34.876954788137 HMNY
| stealth address | amount | amount idx | tag |
| 00: e5836715a4fc4c6835fa883886854a2fc05ff5ad50104587a52aeb1f823b5077 | 34.876954788137 | 5776 of 0 | <fe> |
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": 4662,
"vin": [ {
"gen": {
"height": 4602
}
}
],
"vout": [ {
"amount": 34876954788137,
"target": {
"tagged_key": {
"key": "e5836715a4fc4c6835fa883886854a2fc05ff5ad50104587a52aeb1f823b5077",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 246, 197, 18, 206, 145, 102, 251, 241, 0, 211, 75, 248, 152, 198, 107, 192, 243, 216, 78, 77, 125, 76, 161, 74, 231, 187, 164, 204, 73, 251, 55, 199, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}