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: ade22a38f78462e585cf54a285ace4638f9be5da5a9e858ed501e3f6ed7aa60d
Tx prefix hash: 2192c11aeb975498ccbc1007dd3aa8b7a9a05413635e20fe502a07f716d8e096
Tx public key: b6f20e1e75b459ba7b8574742fc385ce56fe3fa32edb4861bfbd87163ea7b347
| Timestamp: 1779883516 | Timestamp [UTC]: 2026-05-27 12:05:16 | Age [y:d:h:m:s]: 00:012:12:41:31 |
| Block: 2984 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4902 | RingCT/type: yes/0 |
| Extra: 01b6f20e1e75b459ba7b8574742fc385ce56fe3fa32edb4861bfbd87163ea7b34702090000000326697be300 | ||
1 output(s) for total of 34.984754569772 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0ebf61a068435e93984b121e9d14298b32da4c146b2b917c183cb1a5b462b954 | 34.984754569772 | 3540 of 0 | <a0> |
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": 3044,
"vin": [ {
"gen": {
"height": 2984
}
}
],
"vout": [ {
"amount": 34984754569772,
"target": {
"tagged_key": {
"key": "0ebf61a068435e93984b121e9d14298b32da4c146b2b917c183cb1a5b462b954",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 182, 242, 14, 30, 117, 180, 89, 186, 123, 133, 116, 116, 47, 195, 133, 206, 86, 254, 63, 163, 46, 219, 72, 97, 191, 189, 135, 22, 62, 167, 179, 71, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}