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: 43e1421010500db3fab9470a6ce60cecbef0ee98f21b81a38d72349796fef25a
Tx prefix hash: b5fa60158408e0bfc3137d38e0f2e47f967e5229f18b676ec28473d64572650b
Tx public key: 31ec902a650e5fa834aae02e9441aa3c2d77597b5d38ed3e1c28741fefe0711b
| Timestamp: 1779434313 | Timestamp [UTC]: 2026-05-22 07:18:33 | Age [y:d:h:m:s]: 00:017:19:31:15 |
| Block: 83 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7837 | RingCT/type: yes/0 |
| Extra: 0131ec902a650e5fa834aae02e9441aa3c2d77597b5d38ed3e1c28741fefe0711b020900000001a662ed0300 | ||
1 output(s) for total of 35.178869587164 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8715ee541355fd326129015512dc9fceeafe8a60e65e1e7df51e71c7871e6e79 | 35.178869587164 | 79 of 0 | <65> |
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": 143,
"vin": [ {
"gen": {
"height": 83
}
}
],
"vout": [ {
"amount": 35178869587164,
"target": {
"tagged_key": {
"key": "8715ee541355fd326129015512dc9fceeafe8a60e65e1e7df51e71c7871e6e79",
"view_tag": "65"
}
}
}
],
"extra": [ 1, 49, 236, 144, 42, 101, 14, 95, 168, 52, 170, 224, 46, 148, 65, 170, 60, 45, 119, 89, 123, 93, 56, 237, 62, 28, 40, 116, 31, 239, 224, 113, 27, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}