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: 8193f9d95d03ba6671f72c1e1871cd4794348717a973e1e529ca3e96bc0bef38
Tx prefix hash: e7174c13fdda43547c855b75c68623f67e73b21d998abf8e5d126bb61aed3194
Tx public key: 881fe1e0fd15fff7d025a832ac3004932c9ae4ba1024e2c9b7d9e319caa59848
| Timestamp: 1780079553 | Timestamp [UTC]: 2026-05-29 18:32:33 | Age [y:d:h:m:s]: 00:010:07:03:24 |
| Block: 4744 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3142 | RingCT/type: yes/0 |
| Extra: 01881fe1e0fd15fff7d025a832ac3004932c9ae4ba1024e2c9b7d9e319caa5984802090000000226697be300 | ||
1 output(s) for total of 34.867509861527 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4500c2960b4bc7e8b1e0a14cc50c1da0c1b41ba5feca99fc1c7a53cc8bf5542c | 34.867509861527 | 5963 of 0 | <7c> |
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": 4804,
"vin": [ {
"gen": {
"height": 4744
}
}
],
"vout": [ {
"amount": 34867509861527,
"target": {
"tagged_key": {
"key": "4500c2960b4bc7e8b1e0a14cc50c1da0c1b41ba5feca99fc1c7a53cc8bf5542c",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 136, 31, 225, 224, 253, 21, 255, 247, 208, 37, 168, 50, 172, 48, 4, 147, 44, 154, 228, 186, 16, 36, 226, 201, 183, 217, 227, 25, 202, 165, 152, 72, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}