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: 37f54d86284572467ae3c638475de0562f3e20386da371b591a10de4990fb286
Tx prefix hash: 37f4371b3f38845f932be42ebaf41ea4c6577f94b752851572072139840a64f9
Tx public key: f643ea4acb7c40e58c2a970ce7b35e3cba8fe03c036a7196c1e872e5d46b37ab
| Timestamp: 1779971021 | Timestamp [UTC]: 2026-05-28 12:23:41 | Age [y:d:h:m:s]: 00:011:13:12:16 |
| Block: 3848 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4038 | RingCT/type: yes/0 |
| Extra: 01f643ea4acb7c40e58c2a970ce7b35e3cba8fe03c036a7196c1e872e5d46b37ab02090000000a26697be300 | ||
1 output(s) for total of 34.927148894524 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f72369bd5ace8c87d9cfda7be26194df2ce6c2897fcef2845660b387c48bfb0 | 34.927148894524 | 4697 of 0 | <ce> |
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": 3908,
"vin": [ {
"gen": {
"height": 3848
}
}
],
"vout": [ {
"amount": 34927148894524,
"target": {
"tagged_key": {
"key": "6f72369bd5ace8c87d9cfda7be26194df2ce6c2897fcef2845660b387c48bfb0",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 246, 67, 234, 74, 203, 124, 64, 229, 140, 42, 151, 12, 231, 179, 94, 60, 186, 143, 224, 60, 3, 106, 113, 150, 193, 232, 114, 229, 212, 107, 55, 171, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}