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: 4e697c336a012a4fa95eabe0ed961b471bacc2e1adceaef8264c8706f78157e0
Tx prefix hash: 566a6b36a3b97896fcfbc65572ec4fcf123a678edcb97edf4095a8fee99c7ab5
Tx public key: 54c0927f596063a814b174ee4b4963bc43e4e2b14b0455f36c99a648f666c4ab
| Timestamp: 1780701857 | Timestamp [UTC]: 2026-06-05 23:24:17 | Age [y:d:h:m:s]: 00:003:02:11:40 |
| Block: 6065 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1821 | RingCT/type: yes/0 |
| Extra: 0154c0927f596063a814b174ee4b4963bc43e4e2b14b0455f36c99a648f666c4ab020900000001e49593ff00 | ||
1 output(s) for total of 34.779767921011 HMNY
| stealth address | amount | amount idx | tag |
| 00: e1b4ba200911059b97662c3e5b112f9046a0ca4d129fcd56b9b8f57ed5e205ab | 34.779767921011 | 7536 of 0 | <74> |
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": 6125,
"vin": [ {
"gen": {
"height": 6065
}
}
],
"vout": [ {
"amount": 34779767921011,
"target": {
"tagged_key": {
"key": "e1b4ba200911059b97662c3e5b112f9046a0ca4d129fcd56b9b8f57ed5e205ab",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 84, 192, 146, 127, 89, 96, 99, 168, 20, 177, 116, 238, 75, 73, 99, 188, 67, 228, 226, 177, 75, 4, 85, 243, 108, 153, 166, 72, 246, 102, 196, 171, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}