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: ca07174796cd6029e186e7e9a742af2ed0ee68d4901e299093b96e96dc7fd308
Tx prefix hash: 028b59884711e1e4d577405911669e0f1ecf9bdeec6bd5a6b77543495f2aab68
Tx public key: a096965ce8fa8e1d7e59a76e43f2ff7f9431650398a846f5c8666db3b64f9d32
| Timestamp: 1780033308 | Timestamp [UTC]: 2026-05-29 05:41:48 | Age [y:d:h:m:s]: 00:010:19:54:09 |
| Block: 4217 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3669 | RingCT/type: yes/0 |
| Extra: 01a096965ce8fa8e1d7e59a76e43f2ff7f9431650398a846f5c8666db3b64f9d3202090000000226697be300 | ||
1 output(s) for total of 34.905192585528 HMNY
| stealth address | amount | amount idx | tag |
| 00: 52b22fcc2a1b497304a77a391e1b79a21b908bf047dbf74cb6dd135850f2b422 | 34.905192585528 | 5254 of 0 | <09> |
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": 4277,
"vin": [ {
"gen": {
"height": 4217
}
}
],
"vout": [ {
"amount": 34905192585528,
"target": {
"tagged_key": {
"key": "52b22fcc2a1b497304a77a391e1b79a21b908bf047dbf74cb6dd135850f2b422",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 160, 150, 150, 92, 232, 250, 142, 29, 126, 89, 167, 110, 67, 242, 255, 127, 148, 49, 101, 3, 152, 168, 70, 245, 200, 102, 109, 179, 182, 79, 157, 50, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}