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: ad4c7d2a57d5cef723b34d1cb050bc6d608d7b2b775c6146ef2d759c5ba553b0
Tx prefix hash: 5194b77f6edf1fac8c5089639fc091bd50a18224239e5c9fce4f38623a0572f5
Tx public key: eebde18376a1260fca468744028e91a9bb34afcdad2c7860fafee2bb77272d04
| Timestamp: 1780768385 | Timestamp [UTC]: 2026-06-06 17:53:05 | Age [y:d:h:m:s]: 00:002:05:25:48 |
| Block: 6642 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1244 | RingCT/type: yes/0 |
| Extra: 01eebde18376a1260fca468744028e91a9bb34afcdad2c7860fafee2bb77272d04020900000002e49593ff00 | ||
1 output(s) for total of 34.741512407861 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5af54c165cd8e49eacdf663534cd991b38a2362fe4a13e36e4bcd56c1e91d72c | 34.741512407861 | 8188 of 0 | <3b> |
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": 6702,
"vin": [ {
"gen": {
"height": 6642
}
}
],
"vout": [ {
"amount": 34741512407861,
"target": {
"tagged_key": {
"key": "5af54c165cd8e49eacdf663534cd991b38a2362fe4a13e36e4bcd56c1e91d72c",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 238, 189, 225, 131, 118, 161, 38, 15, 202, 70, 135, 68, 2, 142, 145, 169, 187, 52, 175, 205, 173, 44, 120, 96, 250, 254, 226, 187, 119, 39, 45, 4, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}