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: d7d35d8529ea7c216a0b59af235dbe50da453de3cee10a00e69b644f8ced732c
Tx prefix hash: 56acb1eb9ee894dde43ac4bde39854aede373e0b56785244c57bdbe7e54f01d3
Tx public key: 1917bbcb82c0c28d6ea2ac83090eb5b9bbc5ae79c14f30c5ef8cd997f3fd0084
| Timestamp: 1779980537 | Timestamp [UTC]: 2026-05-28 15:02:17 | Age [y:d:h:m:s]: 00:011:08:16:36 |
| Block: 3919 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3967 | RingCT/type: yes/0 |
| Extra: 011917bbcb82c0c28d6ea2ac83090eb5b9bbc5ae79c14f30c5ef8cd997f3fd008402090000000526697be300 | ||
1 output(s) for total of 34.922419314537 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e17c36f57ce7fdd66453b59f42a9c83d7dc56909f4eb20f8bb7569dc164517f | 34.922419314537 | 4813 of 0 | <81> |
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": 3979,
"vin": [ {
"gen": {
"height": 3919
}
}
],
"vout": [ {
"amount": 34922419314537,
"target": {
"tagged_key": {
"key": "3e17c36f57ce7fdd66453b59f42a9c83d7dc56909f4eb20f8bb7569dc164517f",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 25, 23, 187, 203, 130, 192, 194, 141, 110, 162, 172, 131, 9, 14, 181, 185, 187, 197, 174, 121, 193, 79, 48, 197, 239, 140, 217, 151, 243, 253, 0, 132, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}