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: c9e4417e98367119558cfbc4931c20c2b7c60c788e5dc02b55df3f3ad4419c93
Tx prefix hash: a4fd41545fe6fd53da0040aac142a2856d712b2b489b41144e6926daac103dd2
Tx public key: 49a5849319542346ec17b3b077ecb15ba7b8de00b6a911d521be5574d8f6b699
| Timestamp: 1780323097 | Timestamp [UTC]: 2026-06-01 14:11:37 | Age [y:d:h:m:s]: 00:007:11:24:20 |
| Block: 5052 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2834 | RingCT/type: yes/0 |
| Extra: 0149a5849319542346ec17b3b077ecb15ba7b8de00b6a911d521be5574d8f6b69902090000000426697be300 | ||
1 output(s) for total of 34.847032472288 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9efc61ecfbc97a0725a04dedf2d1164e6cdc654739863482ae5b5e130927303 | 34.847032472288 | 6427 of 0 | <51> |
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": 5112,
"vin": [ {
"gen": {
"height": 5052
}
}
],
"vout": [ {
"amount": 34847032472288,
"target": {
"tagged_key": {
"key": "b9efc61ecfbc97a0725a04dedf2d1164e6cdc654739863482ae5b5e130927303",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 73, 165, 132, 147, 25, 84, 35, 70, 236, 23, 179, 176, 119, 236, 177, 91, 167, 184, 222, 0, 182, 169, 17, 213, 33, 190, 85, 116, 216, 246, 182, 153, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}