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: ad6be90b1d9f2a712d1cd5707f9b3a14c67d5e0053f24947ff500c6a6c338f92
Tx prefix hash: cffed0eaa22af44626492ccfcc27099299897361cdc3750bbae017973538f635
Tx public key: 5b44caa2b617abaa6ecaae0bbedb4159ceace5e7ab7b89ff0bfda86569b176f8
| Timestamp: 1779981065 | Timestamp [UTC]: 2026-05-28 15:11:05 | Age [y:d:h:m:s]: 00:011:11:38:43 |
| Block: 3924 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3975 | RingCT/type: yes/0 |
| Extra: 015b44caa2b617abaa6ecaae0bbedb4159ceace5e7ab7b89ff0bfda86569b176f802090000000826697be300 | ||
1 output(s) for total of 34.922086269664 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f22d8f3155b3821c8f3ebaaaea8e2dc63845a1cce28d3adface22b1e0dcda11 | 34.922086269664 | 4821 of 0 | <b2> |
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": 3984,
"vin": [ {
"gen": {
"height": 3924
}
}
],
"vout": [ {
"amount": 34922086269664,
"target": {
"tagged_key": {
"key": "4f22d8f3155b3821c8f3ebaaaea8e2dc63845a1cce28d3adface22b1e0dcda11",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 91, 68, 202, 162, 182, 23, 171, 170, 110, 202, 174, 11, 190, 219, 65, 89, 206, 172, 229, 231, 171, 123, 137, 255, 11, 253, 168, 101, 105, 177, 118, 248, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}