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: 1f89700ee4810a1da8de10aa689a6effdac8d0182cf7a19e14455368ac797594
Tx prefix hash: 3e1b8333ca7b74a699f67c521a7602dd7b08853f700f7f61e91265ba75269950
Tx public key: e8e7639345650416e26998bac8f0878cc46da90c8255fb23ac4f3090dc982b4d
| Timestamp: 1779950430 | Timestamp [UTC]: 2026-05-28 06:40:30 | Age [y:d:h:m:s]: 00:011:18:55:27 |
| Block: 3616 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4270 | RingCT/type: yes/0 |
| Extra: 01e8e7639345650416e26998bac8f0878cc46da90c8255fb23ac4f3090dc982b4d02090000000426697be300 | ||
1 output(s) for total of 34.942607763256 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6d84e3cf0dab79d4aae4827a7d40380faafe523eaa7dabb512abffa9605bf2b | 34.942607763256 | 4367 of 0 | <d0> |
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": 3676,
"vin": [ {
"gen": {
"height": 3616
}
}
],
"vout": [ {
"amount": 34942607763256,
"target": {
"tagged_key": {
"key": "f6d84e3cf0dab79d4aae4827a7d40380faafe523eaa7dabb512abffa9605bf2b",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 232, 231, 99, 147, 69, 101, 4, 22, 226, 105, 152, 186, 200, 240, 135, 140, 196, 109, 169, 12, 130, 85, 251, 35, 172, 79, 48, 144, 220, 152, 43, 77, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}