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: 7b3322a30a21529d7b54ab7d1ac456b0e887f5de55334f7f052974f4ddf12c44
Tx prefix hash: 8c189211ac563924a7e4e99319d6fcf009f87e525071ac02c45584372cbc8788
Tx public key: 71bc7f7d618999b59fc000d8cb7f4df1c7eb5b73147f7c2e0c11e745fc0d117f
| Timestamp: 1780075328 | Timestamp [UTC]: 2026-05-29 17:22:08 | Age [y:d:h:m:s]: 00:010:05:56:45 |
| Block: 4694 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3192 | RingCT/type: yes/0 |
| Extra: 0171bc7f7d618999b59fc000d8cb7f4df1c7eb5b73147f7c2e0c11e745fc0d117f02090000000226697be300 | ||
1 output(s) for total of 34.875858448126 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70bcc86e74697c9fd2ef90fb6524c86320e3faba94a37aff146c6d5fb73eebe5 | 34.875858448126 | 5896 of 0 | <e5> |
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": 4754,
"vin": [ {
"gen": {
"height": 4694
}
}
],
"vout": [ {
"amount": 34875858448126,
"target": {
"tagged_key": {
"key": "70bcc86e74697c9fd2ef90fb6524c86320e3faba94a37aff146c6d5fb73eebe5",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 113, 188, 127, 125, 97, 137, 153, 181, 159, 192, 0, 216, 203, 127, 77, 241, 199, 235, 91, 115, 20, 127, 124, 46, 12, 17, 231, 69, 252, 13, 17, 127, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}