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: 81f8f90bf540639f4e28091dce933cef0cb9eb81ea5acda843e028413f9e8ee2
Tx prefix hash: 3e0f4fdf120fd72520f4cf21ce0cd9b66373236739cb7cf531060f8eb254e01d
Tx public key: 17bd7318c17c28e6a6d7f3ca4a7c7f44dac1db16a1ec0197d58dc7ed1928f183
| Timestamp: 1780718264 | Timestamp [UTC]: 2026-06-06 03:57:44 | Age [y:d:h:m:s]: 00:011:04:24:35 |
| Block: 6215 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2530 | RingCT/type: yes/0 |
| Extra: 0117bd7318c17c28e6a6d7f3ca4a7c7f44dac1db16a1ec0197d58dc7ed1928f183020900000003e49593ff00 | ||
1 output(s) for total of 34.769818763409 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7a182ca28878619cfa9127a1781e9b7b7a91c78911d1dee343cc09a91944357 | 34.769818763409 | 7694 of 0 | <e0> |
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": 6275,
"vin": [ {
"gen": {
"height": 6215
}
}
],
"vout": [ {
"amount": 34769818763409,
"target": {
"tagged_key": {
"key": "c7a182ca28878619cfa9127a1781e9b7b7a91c78911d1dee343cc09a91944357",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 23, 189, 115, 24, 193, 124, 40, 230, 166, 215, 243, 202, 74, 124, 127, 68, 218, 193, 219, 22, 161, 236, 1, 151, 213, 141, 199, 237, 25, 40, 241, 131, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}